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
Comment out step that switches to the new branch #10
Conversation
We decided in https://github.com/orgs/doctrine/teams/doctrinecore/discussions/19 that the default branch should be the lowest one in order to make retargeting branches easier, with the exception of some repositories that may keep that particular step.
Why not just remove it? We have the history in Git. |
This way, it becomes not code but documentation which I believe already exists in other places. I may not understand this concept of templates entirely but it looks like introduces a lot of unnecessary friction being just copy/paste via the UI. The same result could be achieved by publishing the needed code snippets in a README instead of maintaining them in VCS. |
It does a bit more than that, see gif in #2 (comment) for why the files in this repository also come with metadata files and how this works. |
This will have to be approved by those who are going to consume this template with the commented-out part. |
I'd rather have this in "code" commented out. Reasons that come to my mind:
These might be invalid if only I knew what I'm doing with GA, but sadly I don't: I'm installing stuff hoping it'll work as the old release tool used to. Please don't take it as an ignorant's position, I just don't have time to learn about everything that is happening. |
It will be very similar to the previous tool 👍 |
We decided in https://github.com/orgs/doctrine/teams/doctrinecore/discussions/19
that the default branch should be the lowest one in order to make
retargeting branches easier, with the exception of some repositories
that may keep that particular step.