awesome/awesome-go
1
0
Fork 0
mirror of https://github.com/avelino/awesome-go.git synced 2024-09-19 06:06:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add a deadline for new PR on CONTRIBUTION (#1459)

Browse Source 
We are trying to avoid having hundreds of open Pull Requests. By using
this rule we may close old PRs.
This commit is contained in:
Willian Molinari 2017-06-16 16:08:08 -03:00 committed by Avelino
parent 26dde25335
commit a4d360b36c
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -17,6 +17,6 @@ Very good coverage
- [ ] I have added godoc link to the repo and to my pull request
- [ ] I have added coverage service link to the repo and to my pull request
- [ ] I have added goreportcard link to the repo and to my pull request
- [ ] I have read [Contribution guidelines](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#contribution-guidelines) and [Quality standard](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#quality-standard).
- [ ] I have read [Contribution guidelines](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#contribution-guidelines), [maintainers note](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#maintainers) and [Quality standard](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#quality-standard).
Thanks for your PR, you're awesome! :+1:

6
CONTRIBUTING.md
View File

@ -23,7 +23,7 @@ If you removed our PR template you can find it [here](https://github.com/avelino
## Quality standards
To be on the list, project repositories should adhere to these quality standards (http://goreportcard.com/report/**github_user**/**github_repo**):
To be on the list, project repositories should adhere to these quality standards (http://goreportcard.com/report/ **github_user** / **github_repo**):
- Code functions as documented and expected
- Generally useful to the wider community of Go programmers
@ -39,6 +39,10 @@ To be on the list, project repositories should adhere to these quality standards
To make sure every PR is checked, we have [team maintainers](MAINTAINERS). Every PR MUST be reviewed by at least two maintainers before it can get merged.
The maintainers will review your PR and notify you and tag it in case any
information is still missing. They will wait 8 days for your interaction, after
that the PR will be closed.
## Reporting issues