Github Action: Generate and add "release notes" when distributing new builds on Firebase (staging and production)

[Luong Vo (Lucas)]

Why

Currently, the template supports existing CD workflows to distribute new builds to Firebase. There is a space for improvement to have release notes on each build to clarify what is being covered with the new update for the PM and testers instead of showing the default release notes.

Solution: available solutions from TPC

• after merging a PR to develop:

  echo "RELEASE_NOTE_CONTENT="$((git log -1 --merges | grep "\[") | grep . && echo "" || echo $(git log -1 --merges --format=%B))""
  

• after merging a release PR to main

  echo "RELEASE_NOTE_CONTENT="$(git log --merges --pretty=%B $(git describe --abbrev=0 --tags)..HEAD | grep "\[")""
  

Who Benefits?

PM and Testers

[Runchana C. Jingjit]

@luongvo @ryan-conway Let me update the title of this issue for Github action. I'll add more similar to this for Codemagic. 🙏

[Huey]

@lydiasama Since I handled this in the new project, in case you haven't started working on this so would you mind if I handle this for template updates? 😄

[Runchana C. Jingjit]

@hoangnguyen92dn Sure thing. Thank you. 🙏🏻

[Luong Vo (Lucas)]

@hoangnguyen92dn @lydiasama You can consider using https://github.com/mikepenz/release-changelog-builder-action to generate the changelog for release notes on develop and main branches here nimblehq/flutter-templates#270.