Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guidelines for each repository (aka common standard) #7

Closed
wilzbach opened this issue May 16, 2017 · 5 comments
Closed

Guidelines for each repository (aka common standard) #7

wilzbach opened this issue May 16, 2017 · 5 comments
Labels

Comments

@wilzbach
Copy link
Member

I am trying to collect a list of common standard / steps that we should do/enable for each repository:

  1. CI integration
  2. Set master branch to force-push protected (https://github.com/dlang-community/X/settings/branches)

image

  1. Q: Should we set "Require status checks to pass before merging"?

image

For example, with Travis:

image

@ghost
Copy link

ghost commented May 17, 2017

3: Yes. the CI build duration are usually < 2 minutes. Low enough even if something has to be merged in emergency.

@wilzbach
Copy link
Member Author

Okay I have enabled this for all of our maintained repos (except for dsymbol and DGrammar as they don't have a Travis config as of now) and I will soon open a PR that adds this to this README.

Low enough even if something has to be merged in emergency.

FYI: As you are an admin, GH still allows emergency pulls (tough even this could be disabled):

image

Another point that just came to my mind is common docs (see e.g. dlang-community/D-YAML#57).
I guess it wouldn't be too difficult to maintain the same documentation setup for all repos and have one common host (S3, netlify, ...)

@wilzbach
Copy link
Member Author

Another point for the list - thanks to @ZombineDev:

  • enable dmd-nightly and daily cron jobs at Travis

It's a new feature from Travis:

https://docs.travis-ci.com/user/cron-jobs/
https://blog.travis-ci.com/2016-12-06-the-crons-are-here

I have just enabled this on the Travis side and will make PRs for the repos later.

wilzbach added a commit that referenced this issue Jun 22, 2017
Add adoption guidelines and rework README, fixes #6, #7
@wilzbach
Copy link
Member Author

Closed by #10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant