luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Update contribution guidelines

This commit is contained in:
Jim Kalafut 2020-06-11 09:34:25 -07:00 committed by GitHub
parent eb2b1e0b90
commit 8c4a163cbb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CONTRIBUTING.md
View File

@ -13,8 +13,7 @@ rules to get in the way of that.
That said, if you want to ensure that a pull request is likely to be merged, That said, if you want to ensure that a pull request is likely to be merged,
talk to us! You can find out our thoughts and ensure that your contribution talk to us! You can find out our thoughts and ensure that your contribution
won't clash or be obviated by Vault's normal direction. A great way to do this won't clash or be obviated by Vault's normal direction. A great way to do this
is via the [Vault Google Group][2]. Sometimes Vault devs are in `#vault-tool` is via the [Vault Discussion Forum][2].
on Freenode, too.
This document will cover what we're looking for in terms of reporting issues. This document will cover what we're looking for in terms of reporting issues.
By addressing all the points we're looking for, it raises the chances we can By addressing all the points we're looking for, it raises the chances we can
@ -69,7 +68,7 @@ following steps listed in the README, under the section [Developing Vault][1].
[1]: https://github.com/hashicorp/vault#developing-vault [1]: https://github.com/hashicorp/vault#developing-vault
[2]: https://groups.google.com/group/vault-tool [2]: https://discuss.hashicorp.com/c/vault
## Contributor License Agreement ## Contributor License Agreement