-
Notifications
You must be signed in to change notification settings - Fork 54
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
docs: decision record about renaming git branches #177
docs: decision record about renaming git branches #177
Conversation
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.
We should also document e.g. in the CONTRIBUTING.md file, that we are following an modified git flow. But I will also add this to the issue.
docs/development/decision-records/2023-04-03_renaming_branches/README.md
Outdated
Show resolved
Hide resolved
docs/development/decision-records/2023-04-03_renaming_branches/README.md
Show resolved
Hide resolved
docs/development/decision-records/2023-04-03_renaming_branches/README.md
Outdated
Show resolved
Hide resolved
never mind! We have documented it in the DR so that should be enough or? |
…/README.md Co-authored-by: Florian Rusch (ZF Friedrichshafen AG) <[email protected]>
…/README.md Co-authored-by: Florian Rusch (ZF Friedrichshafen AG) <[email protected]>
Yes it should, but I think it is not relevant for contributions all that much. People will have forks, and create PRs with 'main' as base by default. So unless they explicitly target a different branch, it should all be done automatically |
…ecision_record_branch_names
WHAT
This PR adds a decision record about why and how we should rename our Git branches.