- Issue created by @joachim
- 🇳🇱Netherlands bbrala Netherlands
Just noticed your update on your composer project. Sorry.
Thing is we want to make as clear as possible that branch is not to work on, since it WILL be force pushed with updates.
The issuefork is still the default name though? ;x
- 🇬🇧United Kingdom joachim
It looks like the bot also created a '3430259-automated-drupal-11' branch?
> Thing is we want to make as clear as possible that branch is not to work on, since it WILL be force pushed with updates.
Sure, but could it still have the prefix?
Also, without the prefix, the different bot issues for 9/10/11 updates will all have the same branch name which will be a PITA for maintainers as well.
- 🇳🇱Netherlands bbrala Netherlands
Although I agree with you, i'm weary to do this in the current cycle because of the mass renaming that will need to happen. It would also mean new mr's etc etc. :(
I promise to improve this next cycle.
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Glad that I found this ticket, your discussion answers my initial doubt about which branch of the shall I add my extra commits.
Therefore I agree with #2: it should be crystal clear to everyone that the branch “project-update-bot-only” is strictly reserved for the Bot exclusively, it should be considered “read-only” for humans. You can check what output the automation produced during its last run but the ultimate branch that gets merged at the end of the day is the ticket-number-prefixed one will be after all.
“[…] the different bot issues for 9/10/11 updates will all have the same branch name which will be a PITA”
I don't see any problem here:
- Upgrading to D10 → a ticket opens for D10 → a ticket-related repository created for D10 → a ticket-number-prefixed branch to open a merge request with
- Upgrading to D11 → a ticket opens for D11 → a ticket-related repository created for D11 → a ticket-number-prefixed branch to open a merge request with
- Upgrading to D12 → a ticket opens for D12 → you get the point…