generated from insurgent-lab/javascript-lib-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: update repository URL & copyright owner
- Loading branch information
Showing
8 changed files
with
137 additions
and
137 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| { | ||
| "repositoryUrl": "[email protected]:talent-ideal/semantic-release-hex.git", | ||
| "repositoryUrl": "[email protected]:unill-io/semantic-release-hex.git", | ||
| "branches": [ | ||
| "main", | ||
| "next", | ||
|
|
||
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -23,9 +23,9 @@ All types of contributions are encouraged and valued. See the [Table of Contents | |
|
|
||
| ## I Have a Question | ||
|
|
||
| > If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/talent-ideal/semantic-release-hex#readme). | ||
| > If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/unill-io/semantic-release-hex#readme). | ||
| Before you ask a question, it is best to search for existing [Issues](https://github.com/search?q=repo%3Atalent-ideal%2Fsemantic-release-hex+&type=issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first. | ||
| Before you ask a question, it is best to search for existing [Issues](https://github.com/search?q=repo%3Aunill-io%2Fsemantic-release-hex+&type=issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first. | ||
|
|
||
| If you then still feel the need to ask a question and need clarification, we recommend you join the [Discord community](https://discord.gg/cRB8XRFKzH)! We will take care to answer you as soon as possible. | ||
|
|
||
|
|
@@ -42,8 +42,8 @@ If you then still feel the need to ask a question and need clarification, we rec | |
| A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible. | ||
|
|
||
| - Make sure that you are using the latest version. | ||
| - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/talent-ideal/semantic-release-hex#readme). If you are looking for support, you might want to check [this section](#i-have-a-question)). | ||
| - Perform a [search](https://github.com/search?q=repo%3Atalent-ideal%2Fsemantic-release-hex+&type=issues) to see if the bug/error has already been reported. If it has, add a comment to the existing issue instead of opening a new one. | ||
| - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/unill-io/semantic-release-hex#readme). If you are looking for support, you might want to check [this section](#i-have-a-question)). | ||
| - Perform a [search](https://github.com/search?q=repo%3Aunill-io%2Fsemantic-release-hex+&type=issues) to see if the bug/error has already been reported. If it has, add a comment to the existing issue instead of opening a new one. | ||
| - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue. | ||
| - Collect information about the bug: | ||
| - Stack trace (Traceback) | ||
|
|
@@ -56,7 +56,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform | |
|
|
||
| We use GitHub issues to track bugs and errors. If you run into an issue with the project: | ||
|
|
||
| - Open a [Bug report issue](https://github.com/talent-ideal/semantic-release-hex/issues/new/choose). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.) | ||
| - Open a [Bug report issue](https://github.com/unill-io/semantic-release-hex/issues/new/choose). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.) | ||
| - Explain the behavior you would expect and the actual behavior. | ||
| - Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case. | ||
| - Provide the information you collected in the previous section. | ||
|
|
@@ -74,15 +74,15 @@ This section guides you through submitting an enhancement suggestion for `semant | |
| #### Before Submitting an Enhancement <!-- omit in toc --> | ||
|
|
||
| - Make sure that you are using the latest version. | ||
| - Read the [documentation](https://github.com/talent-ideal/semantic-release-hex#readme) carefully and find out if the functionality is already covered, maybe by an individual configuration. | ||
| - Perform a [search](https://github.com/search?q=repo%3Atalent-ideal%2Fsemantic-release-hex+&type=issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. | ||
| - Read the [documentation](https://github.com/unill-io/semantic-release-hex#readme) carefully and find out if the functionality is already covered, maybe by an individual configuration. | ||
| - Perform a [search](https://github.com/search?q=repo%3Aunill-io%2Fsemantic-release-hex+&type=issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. | ||
| - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library. | ||
|
|
||
| #### How Do I Submit a Good Enhancement Suggestion? <!-- omit in toc --> | ||
|
|
||
| Enhancement suggestions are tracked as [GitHub issues](https://github.com/talent-ideal/semantic-release-hex/issues). | ||
| Enhancement suggestions are tracked as [GitHub issues](https://github.com/unill-io/semantic-release-hex/issues). | ||
|
|
||
| - Open a [Feature request issue](https://github.com/talent-ideal/semantic-release-hex/issues/new/choose). | ||
| - Open a [Feature request issue](https://github.com/unill-io/semantic-release-hex/issues/new/choose). | ||
| - Use a **clear and descriptive title** for the issue to identify the suggestion. | ||
| - Provide a **step-by-step description of the suggested enhancement** in as many details as possible. | ||
| - **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you. | ||
|
|
@@ -100,7 +100,7 @@ $ git clone [email protected]:<your-username>/semantic-release-hex.git # or https:/ | |
| # Navigate to the newly cloned directory | ||
| $ cd semantic-release-hex | ||
| # Assign the original repo to a remote called "upstream" | ||
| $ git remote add upstream [email protected]:talent-ideal/semantic-release-hex.git # or https://github.com/talent-ideal/semantic-release-hex.git for HTTPS | ||
| $ git remote add upstream [email protected]:unill-io/semantic-release-hex.git # or https://github.com/unill-io/semantic-release-hex.git for HTTPS | ||
| # Install the dependencies | ||
| $ npm install | ||
| ``` | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| sonar.projectKey=Talent-Ideal_semantic-release-hex | ||
| sonar.organization=talent-ideal | ||
| sonar.projectKey=unill-io_semantic-release-hex | ||
| sonar.organization=unill-io | ||
| sonar.coverage.exclusions=tests/**,**.spec.js | ||
| sonar.javascript.lcov.reportPaths=./coverage/lcov.info |