You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ The [Project Team](#join-the-project-team) looks forward to your contributions.
33
33
34
34
If you have a question about this project, how to use it, or just need clarification about something:
35
35
36
-
* Open an Issue at https://github.com/shinsenter/defer.js/issues
36
+
* Open an Issue at https://code.shin.company/defer.js/issues
37
37
* Provide as much context as you can about what you're running into.
38
38
* Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant. If not, please be ready to provide that information if maintainers ask for it.
39
39
@@ -47,7 +47,7 @@ Once it's filed:
47
47
48
48
If you run into an error or bug with the project:
49
49
50
-
* Open an Issue at https://github.com/shinsenter/defer.js/issues
50
+
* Open an Issue at https://code.shin.company/defer.js/issues
51
51
* Include *reproduction steps* that someone else can follow to recreate the bug or error on their own.
52
52
* Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant. If not, please be ready to provide that information if maintainers ask for it.
53
53
@@ -63,7 +63,7 @@ Once it's filed:
63
63
64
64
If the project doesn't do something you need or want it to do:
65
65
66
-
* Open an Issue at https://github.com/shinsenter/defer.js/issues
66
+
* Open an Issue at https://code.shin.company/defer.js/issues
67
67
* Provide as much context as you can about what you're running into.
68
68
* Please try and be clear about why existing features and alternatives would not work for you.
69
69
@@ -106,7 +106,7 @@ To contribute documentation:
106
106
* Make sure your changes are formatted correctly and consistently with the rest of the documentation.
107
107
* Re-read what you wrote, and run a spellchecker on it to make sure you didn't miss anything.
108
108
* Write clear, concise commit message(s) using [conventional-changelog format](https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/convention.md). Documentation commits should use `docs(<component>): <message>`.
109
-
* Go to https://github.com/shinsenter/defer.js/pulls and open a new pull request with your changes.
109
+
* Go to https://code.shin.company/defer.js/pulls and open a new pull request with your changes.
110
110
* If your PR is connected to an open issue, add a line in your PR's description that says `Fixes: #123`, where `#123` is the number of the issue you're fixing.
111
111
112
112
Once you've filed the PR:
@@ -132,7 +132,7 @@ To contribute code:
132
132
* Write tests that verify that your contribution works as expected.
133
133
* Write clear, concise commit message(s) using [conventional-changelog format](https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/convention.md).
134
134
* Dependency updates, additions, or removals must be in individual commits, and the message must use the format: `<prefix>(deps): PKG@VERSION`, where `<prefix>` is any of the usual `conventional-changelog` prefixes, at your discretion.
135
-
* Go to https://github.com/shinsenter/defer.js/pulls and open a new pull request with your changes.
135
+
* Go to https://code.shin.company/defer.js/pulls and open a new pull request with your changes.
136
136
* If your PR is connected to an open issue, add a line in your PR's description that says `Fixes: #123`, where `#123` is the number of the issue you're fixing.
137
137
138
138
Once you've filed the PR:
@@ -153,7 +153,7 @@ Sometimes, the `support` label will be added to things that turn out to actually
153
153
154
154
In order to help other folks out with their questions:
155
155
156
-
* Go to the issue tracker and [filter open issues by the `support` label](https://github.com/shinsenter/defer.js/issues?q=is%3Aopen+is%3Aissue+label%3Asupport).
156
+
* Go to the issue tracker and [filter open issues by the `support` label](https://code.shin.company/defer.js/issues?q=is%3Aopen+is%3Aissue+label%3Asupport).
157
157
* Read through the list until you find something that you're familiar enough with to give an answer to.
158
158
* Respond to the issue with whatever details are needed to clarify the question, or get more details about what's going on.
159
159
* Once the discussion wraps up and things are clarified, either close the issue, or ask the original issue filer (or a maintainer) to close it for you.
@@ -170,7 +170,7 @@ Some notes on picking up support issues:
170
170
171
171
One of the most important tasks in handling issues is labeling them usefully and accurately. All other tasks involving issues ultimately rely on the issue being classified in such a way that relevant parties looking to do their own tasks can find them quickly and easily.
172
172
173
-
In order to label issues, [open up the list of unlabeled issues](https://github.com/shinsenter/defer.js/issues?q=is%3Aopen+is%3Aissue+no%3Alabel) and, **from newest to oldest**, read through each one and apply issue labels according to the table below. If you're unsure about what label to apply, skip the issue and try the next one: don't feel obligated to label each and every issue yourself!
173
+
In order to label issues, [open up the list of unlabeled issues](https://code.shin.company/defer.js/issues?q=is%3Aopen+is%3Aissue+no%3Alabel) and, **from newest to oldest**, read through each one and apply issue labels according to the table below. If you're unsure about what label to apply, skip the issue and try the next one: don't feel obligated to label each and every issue yourself!
174
174
175
175
Label | Apply When | Notes
176
176
--- | --- | ---
@@ -205,7 +205,7 @@ To clean up issues and PRs:
205
205
* not marked as `starter` or `help wanted` (these might stick around for a while, in general, as they're intended to be available)
206
206
* no explicit messages in the comments asking for it to be left open
207
207
* does not belong to a milestone
208
-
* Leave a message when closing saying "Cleaning up stale issue. Please reopen or ping us if and when you're ready to resume this. See https://github.com/shinsenter/defer.js/blob/latest/CONTRIBUTING.md#clean-up-issues-and-prs for more details."
208
+
* Leave a message when closing saying "Cleaning up stale issue. Please reopen or ping us if and when you're ready to resume this. See https://code.shin.company/defer.js/blob/latest/CONTRIBUTING.md#clean-up-issues-and-prs for more details."
Copy file name to clipboardExpand all lines: README.md
+14-14
Original file line number
Diff line number
Diff line change
@@ -2,24 +2,24 @@
2
2
3
3
🥇 A super small, super efficient library that helps you lazy load almost everything like images, video, audio, iframes as well as stylesheets, and JavaScript.
[](https://snyk.io/advisor/npm-package/@shinsenter/defer.js)
🚀 A Laravel package that focuses on minimizing payload size of HTML document and optimizing processing on the browser when rendering the web page.
801
801
@@ -804,9 +804,9 @@ In this library, a closure is a [Function](#Function) that gives you access to a
804
804
805
805
[](https://www.paypal.me/shinsenter)
806
806
[](https://www.patreon.com/appseeds)
807
-
[](https://github.com/shinsenter/defer.js/stargazers)
808
-
[](https://github.com/shinsenter/defer.js/issues/new)[](https://gitter.im/shinsenter/defer.js?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
809
-
807
+
[](https://code.shin.company/defer.js/stargazers)
808
+
[](https://code.shin.company/defer.js/issues/new)
809
+
[](https://gitter.im/shinsenter/defer.js?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
0 commit comments