Skip to content

Conversation

@VolkerHartmann
Copy link
Contributor

Add docu for handling forks in README.md

- Remove this section from README.md
- Push changes to GitHub
- `git add .`
- `git push -u origin firstSettings`
Copy link
Contributor Author

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!

@Pfeil
Copy link
Member

Pfeil commented Sep 28, 2021

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.

@ThomasJejkal
Copy link
Contributor

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.

@Pfeil
Copy link
Member

Pfeil commented Nov 16, 2021

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?

@ThomasJejkal
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants