Hello,
As indicated previously, we extended the code freeze until today due to some major changes in the jbosstools github repositories. in short, we changed the default branch from 'master' to 'main'. ( see
https://issues.redhat.com/browse/JBIDE-28036 )
This move is now complete. All the active jbosstools and jbdevstudio repositories are using 'main' branch as default.
On GitHub side, the migration automatically took care of open prs, draft, rules and also takes care of redirecting users to the correct branch (
https://github.com/github/renaming )
On your side, depending on how you configured your remote, you may have errors when fetching the repository.
there are two options :
- fetching will automatically change the remote tracked branch from master to main.
- fetching will fail with an error saying the remote branch cannot be resolved.
if you experience the second case scenario, here are the steps to perform in the corresponding directory to switch the remote config :
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
In all cases, if you had a local 'master' branch, it will remain named like it, but the remote-tracking branch should be changed to origin/main.
CI and GitHub actions were also patched. If you experience any issues, please let us know.
This also ends the code freeze, all main branches are now open for PRs.
Regards,
