| Re: [jakartaee-spec-project-leads] GitHub bots failing ECA validation |
I think you can just override and merge as a committer as there isn’t an IP issue as it is a project bot.
From:jakartaee-spec-project-leads-bounces@xxxxxxxxxxx <jakartaee-spec-project-leads-bounces@xxxxxxxxxxx>
On Behalf Of Tom Jenkinson
Sent: 11 June 2020 10:42
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>;
Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [jakartaee-spec-project-leads] GitHub bots failing ECA validation
Hi,
Is there any update on when and how pull requests which contain commits from known bots (such as jta-bot) will be able to be included in branches which are checked for ECA? The latest I see on https://bugs.eclipse.org/bugs/show_bug.cgi?id=552628indicates to me that it is not possible yet.
Commits from these bots will go into unprotected branches and tags (presumably because they are unprotected), but can't get on a protected branch - failing a validation check for the PR. For now, that means that a release branch cannot be synced back into master.
Perhaps we might need to change https://wiki.eclipse.org/JakartaEE_New_Infra_Release_Jobsuch that it doesn't use a bot to create new commits and that becomes part of the role of the person that releases a version so these branches can be synced back?
Thanks,
Tom_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads