-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use main
as primary branch
#7126
Comments
Hello Sir @lemeurherve I am currently trying to solve this issue.But I have doubt regarding Updating jobs in ci.jenkins.io, infra.ci.jenkins.io, and trusted.ci.jenkins.io. For doing this part do I need more access or so? Please let me know |
Hi @biru-codeastromer , you won't be given more accesses (as these resources are sensitive and require certain level of trust), but if you can elaborate a list of all locations in which you see code related to this change, you might be able to help by preparing PRs once we've given you the green light.
Be aware that there are also private documents which might require updates (we'll take care of them). |
Hi @dduportal Sir , Thank you for the clarification and for trusting me with this contribution! I completely understand the sensitivity of these resources and appreciate the opportunity to assist within the provided scope. I’ll begin by carefully analyzing the codebase to prepare an exhaustive list of all the locations where the changes are required, including code references and relevant "locations" like specific jobs or configurations. Btw I noticed that the sites infra.ci.jenkins.io, and trusted.ci.jenkins.io didn't open ;the links got errors. Once I’ve compiled the list, I’ll share it for your review before moving forward with any PRs. Please feel free to let me know if there are any specific guidelines or additional considerations I should keep in mind while preparing the list. Looking forward to your feedback! |
Suggestion
We should use
main
instead ofmaster
as primary branch.This will need updating not only this repo but also all references to
master
in Jenkinsfile(s) and job on ci.jenkins.io, infra.ci.jenkins.io and trusted.ci.jenkins.ioLinks
The text was updated successfully, but these errors were encountered: