Elgato_dark/IGListKit
1
0
Fork 0
mirror of https://github.com/Instagram/IGListKit synced 2026-05-06 06:58:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
IGListKit/.github/RELEASE_CHECKLIST.md
Tim Oliver 2ed59fcf80 Update 'master' branch references to 'main' branch 
Summary:
G'day folks! As promised, I'm spending a bit of my free time seeing what I can do to update and refresh the IGListKit repo on GitHub.

I noticed last night some strange behaviour in that the GitHub Actions CI wasn't running when new commits were merged into the main branch. I discovered the cause of this was because the `CI.yml` file still had `master` in its build rules instead of `main`. And once I noticed that, I noticed there were a lot of other references to the main branch being called `master` in a lot of the documentation.

Thankfully within the documentation, GitHub was smart enough to automatically redirect all of the `master` URLs to `main`, so nothing visibly broke, but I definitely think we should update all of that. :)

I went through the entire repo and did a thorough audit in all of its text files, and updated the main branch name accordingly.

Reviewed By: DimaVartanian

Differential Revision: D42990133

fbshipit-source-id: d6b06c40b1b959990856b46b048895e3c55a9870
2023-02-08 18:34:25 -08:00

817 B
Raw Blame History

Release Checklist

Here are the steps for creating and publishing a new release for IGListKit.

  • Final review and update of header docs and guides
  • Final review of changelog
  • Regenerate docs
  • Update pod spec version
  • Update xcodeproj version
  • Run pod install on all examples (must happen on FB internal because of sync issues)
  • Merge main into stable via cmd-line and push
  • Confirm stable is 0|0 ahead/behind
  • Create GitHub release from stable
  • Paste changelog into GH release notes
  • Publish GitHub release
  • Run pod lib lint
  • Push updated podspec: pod trunk push IGListKit.podspec
  • Verify new release on CocoaPods
  • Tweet all the tweets