🐕 Batch: Have a main branch at Ersilia?

[miquelduranfrigola]

Summary

The below has been written with ChatGPT assistance

Background

Since October 2020, GitHub has defaulted to main as the primary branch name instead of master. Many projects have adopted this change for consistency, inclusivity, and alignment with modern tooling.

Current State

• Our repository currently uses master as the default branch.
• Some tools, scripts, and external integrations assume main as the default branch, requiring manual adjustments.
• New contributors might expect main and be confused by master.

Potential Approaches

1. Keep master as the Default – Maintain the current setup.
2. Rename master to main – Align with modern standards and tooling.
3. Maintain Both Branches – Have both master and main coexist, allowing flexibility for different workflows.

Questions for the Community

• Should we keep master as the default branch, rename it to main, or maintain both?
• Are there any concerns or dependencies that might be affected by these choices?
• What is the preferred workflow for contributors and maintainers?

Next Steps

Based on the feedback from this discussion, we can determine the best approach for our repository moving forward. Please share your thoughts!

Objective(s)

• Decide the approach (i.e. rename, duplicate, etc.)
• Implement

Documentation

No response

[GemmaTuron]

If it is not very problematic I'd rename to main

[miquelduranfrigola]

It may be a bit problematic for the workflows and the scripts that download from raw.githubusercontent ...

[GemmaTuron]

Well if we have all of them centralised in one repo that should be fine to change. Do we consider moving Ersilia's workflows to a single repo as well?

[miquelduranfrigola]

I don't think it is necessary to move the workflows to a separate repo.