chore: replace "master" with "main"

[biru-codeastromer]

Fixes #7126

Description:

This PR replaces all instances of master with main in the codebase, documentation, and GitHub workflows.

Changes include:

• Updated Jenkinsfiles.
• Updated documentation (README.adoc, CONTRIBUTING.adoc).
• Updated GitHub workflows and configurations.

Please review and let me for further improvements !

[biru-codeastromer]

updated the branch .

[MarkEWaite]

This seems like a lot of work with many, many opportunities for issues, without me being confident that @biru-codeastromer is ready for the weeks or months of issues that will result from the change.

Have you checked the other documentation generation locations that contribute to the jenkins.io site, like the backend extension indexer and the pipeline steps documentation generator? Have you investigated the changelog generator tooling to confirm that it will continue to submit pull requests that are targeting the correct branch?

[biru-codeastromer]

This seems like a lot of work with many, many opportunities for issues, without me being confident that @biru-codeastromer is ready for the weeks or months of issues that will result from the change.

Have you checked the other documentation generation locations that contribute to the jenkins.io site, like the backend extension indexer and the pipeline steps documentation generator? Have you investigated the changelog generator tooling to confirm that it will continue to submit pull requests that are targeting the correct branch?

Hi Sir ,

Thanks for your constructive feedback! I completely understand that such a broad change comes with long-term implications, and I appreciate your insights and concerns.

Regarding your concerns:
-I haven’t yet checked the backend extension indexer and pipeline steps documentation generator. I will investigate these and provide an update.
-I’ll verify whether the changelog generator will still correctly submit PRs to the correct branch and ensure no unintended side effects.

I thought it would be better to raise a PR for improvements, so I prepared this as a draft to initiate discussions and track areas that need further research. Since there’s still work and investigation left, you can keep this PR in draft mode while I continue my research.

If you believe this is doable for me, I’d be happy to continue working on it.

Thanks again Sir for your valuable feedback! Much appreaciated

[zbynek]

The list of files in #7126 also includes the issue templates, I think they should be included in the PR.

[biru-codeastromer]

The list of files in #7126 also includes the issue templates, I think they should be included in the PR.

Thanks for the feedback ! Will be including them in the PR now .

[biru-codeastromer]

The list of files in #7126 also includes the issue templates, I think they should be included in the PR.

I have added !

[biru-codeastromer]

this file : "jenkins.io/updatecli/values.github-action.yaml" too has it as :

github:
  user: "GitHub Actions"
  email: "41898282+github-actions[bot]@users.noreply.github.com"
  username: "github-actions"
  token: "UPDATECLI_GITHUB_TOKEN"
  branch: "master"
  owner: "jenkins-infra"
  repository: "jenkins.io"

[kmartens27]

Hi @biru-codeastromer, is this intended to just be the jenkins.io github repo documentation update, or would the jenkins.io documentation pages be updated in this PR as well? I ask because when reviewing the documentation on jenkins.io, there are several uses of the master URL that would be updated here.

If that will be a separate PR, please let me know and I'm happy to help gather all the usages and create a draft PR to make the accompanying updates.

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[biru-codeastromer]

for my latest pr , the conflicts came here will be fixing it now

[biru-codeastromer]

done !