You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not intending to single out auditjs, but I'm gonna use this Issue to collect some notes on converting projects to use a "main" branch instead of a "master" branch. Hopefully this is of use to others. Please add your learnings too!
Update README.md links that refer to master to refer to main, like logos, images, etc.
CircleCI - so far our configs for CircleCI have not required any sort of changes. If your config.yml mentions the master branch by name for any reason, you might need to make changes, but so far, we've not needed any changes. Noice!
Jenkins (internal builds) - So far, two main steps:
In Jenkins Web UI config, change Pipeline "Branches to build" -> "Branch Specifier (blank for 'any')" from: */master
to: */main
In the Jenkinsfile, change the "dockerizedBuildPipeline" to include a deployBranch value to override the current default:
Failure to do this step will cause the Jenkins build to "skip" the "Deploy" and "Post Deploy" steps, but will not cause an obvious build failure. Such a case is shown below:
Replace use of terms that may be offensive, e.g. whitelist
Related: keep an eye out for changing names of source code branches, e.g. master to main
cc @bhamail / @DarthHater / @allenhsieh / @ken-duck
The text was updated successfully, but these errors were encountered: