Hi Frank,

On Tue, Jun 15, 2021 at 2:10 PM Frank Langelage <frank@lafr.de> wrote:
Step 3 throws an error for me:

jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git branch -m
master main

jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git fetch origin
remote: Enumerating objects: 326, done.
remote: Counting objects: 100% (326/326), done.
remote: Compressing objects: 100% (189/189), done.
remote: Total 326 (delta 168), reused 286 (delta 131), pack-reused 0
Receiving objects: 100% (326/326), 64.65 KiB | 23.00 KiB/s, done.
Resolving deltas: 100% (168/168), completed with 41 local objects.
 From github.com:/langfr/wildfly-core

I suspect this ^^^ is your problem. The instructions assume 'origin' points to wildfly/wildfly-core, not langfr/wildfly-core. So instead of origin you should use the name of the remote you use for wildfly/wildfly-core.

  * [new branch]      15.x       -> origin/15.x

jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git branch -u
origin/main main
error: the requested upstream branch 'origin/main' does not exist
hint: If you are planning on basing your work on an upstream
hint: branch that already exists at the remote, you may need to
hint: run "git fetch" to retrieve it.
hint: If you are planning to push out a new local branch that
hint: will track its remote counterpart, you may want to use
hint: "git push -u" to set the upstream config as you push.

jboss@sb2000:/home/jboss/WildFly-Core-master/wildfly-core git status
On branch main
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
   (use "git add <file>..." to update what will be committed)
   (use "git checkout -- <file>..." to discard changes in working directory)


no changes added to commit (use "git add" and/or "git commit -a")

Am 15.06.2021 um 09:44 schrieb Jean-Frederic Mesnil:
> Hi,
> The renaming of “master" to “main” branch for wildfly-core is over.
> If you go to https://github.com/wildfly/wildfly-core, 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-core, you have nothing
> to do, the change is automatic.
> The CI has been updated and I verified the PR jobs runs fine (from
> https://ci.wildfly.org/project/WildFlyCore_PullRequest?mode=builds).
> I tried to do a thorough change in all the WildFly Core jobs on
> https://ci.wildfly.org/project/WildFlyCore?mode=builds and most of the
> jobs are fine too.
> Best regards,
> Jeff
> --
> Jeff Mesnil
> Principal Software Engineer
> Red Hat
> http://jmesnil.net/
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org

Brian Stansberry
Principal Architect, Red Hat JBoss EAP