FYI re the below. Delivery from the wildfly-dev list was disrupted for a
number of weeks so many subscribers likely were unaware of this thread.
On Thu, Jul 29, 2021 at 3:47 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
The renaming of “master" branch to “main” for wildfly is
complete. If you
go to
https://github.com/wildfly/wildfly, you should have a notification
to update your local environment. This includes running the following
commands: —8<— git branch -m master main git fetch origin git branch -u
origin/main main git remote set-head origin -a —8<— If you have opened PR
against wildfly/wildfly, you have nothing to do, the change is automatic.
If you go to your personal 'wildfly' repo on Github it will notify you
that wildfly/wildfly has made this change and will suggest that you make
the same change to your own 'master'. It provides a link to how to do that,
which is documented at
https://docs.github.com/en/github/administering-a-repository/managing-bra...
.
The CI has been updated and the PR jobs (from
https://ci.wildfly.org/project.html?projectId=WF_PullRequest) appear to
be working fine. I tried to do a thorough change in all the WildFly jobs on
https://ci.wildfly.org/project.html?projectId=WF and the relevant WildFly
Core jobs on
https://ci.wildfly.org/project/WildFlyCore?mode=builds. I believe they
should be fine; we'll see how the overnight runs go.
Best regards, Brian
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His