support develop to main rename on nebari repo

[Adam-D-Lewis]

Reference Issues or PRs

Related to nebari-dev/nebari#2748

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Documentation

Access-centered content checklist

Text styling

• The content is written with plain language (where relevant).
• If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• All links describe where they link to (for example, check the Nebari website).
• This content adheres to the Nebari style guides.

Non-text content

• All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing GIFs or videos.
• If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

[netlify]

✅ Deploy Preview for nebari-docs ready!

Name	Link
🔨 Latest commit	67fc433
🔍 Latest deploy log	https://app.netlify.com/sites/nebari-docs/deploys/673378ae8eb25b0008d06756
😎 Deploy Preview	https://deploy-preview-532--nebari-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[marcelovilla]

Thanks @Adam-D-Lewis !

[viniciusdc]

I think this is good to keep:

#### Hotfixes

If a patch or hotfix release is needed, the release process is the same as outlined above. The only difference is that the commits merged into the hotfix release branch will need to be cherry-picked from the `main` branch.

[Adam-D-Lewis]

Yes, at the time I thought we didn't want to do hotfixes this way anymore, but we promptly did exactly that. Happy to add it back in.

[Adam-D-Lewis]

I looked at this again today. The hotfix release process is also captured in the template that is linked to so I don't see the need for an explanation here as well. I think it's easier to keep the docs up to date if we just point to one place for updates rather than needing to update various places.

[Adam-D-Lewis]

@viniciusdc ^

[viniciusdc]

LGTM, thanks @Adam-D-Lewis -- the rework on the release process itself will be done as part of #433