-
Notifications
You must be signed in to change notification settings - Fork 2
Add docu for working with forks #3
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
base: master
Are you sure you want to change the base?
Add docu for working with forks #3
Conversation
| - Remove this section from README.md | ||
| - Push changes to GitHub | ||
| - `git add .` | ||
| - `git push -u origin firstSettings` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
git commit is missing here!
|
I like the idea to put this into the readme actually, because it is more visible than the wiki (which is an extra repo), the readme needs to be adjusted anyway and it is needed one time in each copy only. |
|
Not sure if I'm invited to this discussion, but anyways, I just join. ;-) Don't you think that things like defined workflows belong to a CONTRIBUTING.md file? From README it might be removed and replaced by project specific content. |
|
I think this is not about contributing but how to adapt the template, which is done once for every repository and can then be deleted, isn't it? |
|
The README.md, yes, for information on how to use this template and on what to adapt after instantiation time. But the development workflow including branching strategy and stuff like that is decoupled from the project template and rather something that should be defined on a project-basis. Thus. I thought we could put this in CONTRIBUTING.md as some kind of good practice for our projects which should be followed for all of them. |
Add docu for handling forks in README.md