Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Migrate default branch from `master` to `main`

Open
  • Is something wrong?
#491 0 comments 0 reactions 1 assignee View on GitHub

@ravi-prakash-v is already working on this.

Since Sep 24, 2025.

Assessment

This issue has not been assessed yet.

Description

working group meeting

📌 Description

The repository currently uses the master branch as its default. To align with modern, inclusive standards and GitHub’s default conventions, we need to:

  • Officially deprecate master
  • Transition to main as the new default branch
  • Update all references across the repo and community workflows

🎯 Rationale

  • Inclusivity: Industry-wide shift to using main instead of master.
  • Consistency: Aligns Beckn Protocol repos with open-source best practices.
  • Compatibility: Many CI/CD and automation tools expect main as the default.

✅ Tasks

  • Change default branch in GitHub repository settings from master → main.

  • Ensure main is protected with the same branch protection rules as master.

  • Update references to master in:

    • Documentation files
    • CI/CD configurations
    • Contribution guidelines
    • Governance references

  • Notify community via Announcement (see linked PR/Discussion).

  • Add redirects/aliases where necessary to avoid broken links.

🔄 Community Instructions

Contributors are requested to:

  • Update local branches (git branch -m master main).
  • Rebase any open PRs onto main.
  • Update Issues, Discussions, and documentation references pointing to master.

📎 References

🔔 Impact: Medium — Requires community coordination but no breaking changes to specifications.

Dominant language
No language data
Stars
454
Forks
127
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beckn/protocol-specifications

All issues in beckn/protocol-specifications

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.