-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #96 from Ensono/6795-update-amido-references
update amido to ensono references
- Loading branch information
Showing
4 changed files
with
11 additions
and
11 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 |
---|---|---|
|
@@ -35,10 +35,10 @@ The basis of all is to remember to do good humaning. Everyone is on their own pa | |
* Tests aren't optional | ||
|
||
# How to contribute | ||
Unsure where to being? Start by looking through the following [issues](https://github.com/amido/stacks/issues?q=is%3Aissue+is%3Aopen+sort%3Acomments-desc) labels: | ||
Unsure where to being? Start by looking through the following [issues](https://github.com/ensono/stacks-terraform/issues?q=is%3Aissue+is%3Aopen+sort%3Acomments-desc) labels: | ||
|
||
* [good-first-issue](https://github.com/amido/stacks/labels/good-first-issue) - should only require a few lines of code, and a test or two. | ||
* [documentation](https://github.com/amido/stacks/labels/kind%2Fdocumentation) - we always need to improve our documentation, it's one of the best ways to contribute. | ||
* [good-first-issue](https://github.com/ensono/stacks-terraform/labels/good-first-issue) - should only require a few lines of code, and a test or two. | ||
* [documentation](https://github.com/ensono/stacks-terraform/labels/kind%2Fdocumentation) - we always need to improve our documentation, it's one of the best ways to contribute. | ||
|
||
Sorting the issues by number of comments generally gives a reasonable proxy for the impact the change will have. More comments, more vested interest. | ||
|
||
|
@@ -59,11 +59,11 @@ We actively welcome your pull requests: | |
2. If you've added code that should be tested, add tests. | ||
3. Update the documentation. | ||
4. Ensure the test suite passes. | ||
5. Issue the pull request using the repos PULL_REQUEST_TEMPLATE.md. It's important to link the [issue number](https://github.com/amido/stacks/issues) to ensure that the Issue is closed. | ||
5. Issue the pull request using the repos PULL_REQUEST_TEMPLATE.md. It's important to link the [issue number](https://github.com/ensono/stacks-terraform/issues) to ensure that the Issue is closed. | ||
|
||
## How to report a bug | ||
### Security first | ||
If you find a security vulnerability, do NOT open an [issue](https://github.com/amido/stacks/issues/new/choose). Email [Amido](mailto:[email protected]) instead. | ||
If you find a security vulnerability, do NOT open an [issue](https://github.com/ensono/stacks-terraform/issues/new/choose). Email [Amido](mailto:[email protected]) instead. | ||
|
||
If you aren't sure you've found an security issue, ask yourself the following: | ||
1. Can I access something that is not mine? | ||
|
@@ -72,7 +72,7 @@ If you aren't sure you've found an security issue, ask yourself the following: | |
If you answered "yes" to either question, please get in contact. | ||
|
||
### Report bugs using Github issues | ||
We use GitHub issues to track public bugs. Report a bug by opening a new issue. Please follow the [issue templates](https://github.com/amido/stacks/tree/master/.github/ISSUE_TEMPLATE). | ||
We use GitHub issues to track public bugs. Report a bug by opening a new issue. Please follow the [issue templates](https://github.com/ensono/stacks-terraform/tree/master/.github/ISSUE_TEMPLATE). | ||
|
||
In general, please follow the guidelines: | ||
* A quick summary and/or background | ||
|
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