Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#198] Generate and add "release notes" when distributing new builds on Firebase (staging and production) #270

Merged
merged 3 commits into from
Nov 13, 2023

Conversation

doannimble
Copy link
Contributor

@doannimble doannimble commented Sep 25, 2023

What happened 👀

  • Use mikepenz/release-changelog-builder-action to generate change log
  • Find and use HEAD commit for prudction build
  • Apply Limit changelog to the latest pull request only for staging
  • Add changelog-config.json file

Insight 📝

  • I was trying to use echo "RELEASE_NOTE_CONTENT="$((git log -1 --merges | grep "\[") | grep . && echo "" || echo $(git log -1 --merges --format=%B))"" for staging flow (android and iOS)

and Add echo "RELEASE_NOTE_CONTENT="$(git log --merges --pretty=%B $(git describe --abbrev=0 --tags)..HEAD | grep "\[")"" for production flow (Android only)

But neither of them works (showing empty value)

  • Trying with `8BitJonny/gh-get-current-pr is better, but it still does not meet our expectations. It is only able to get the PR title/content in raw text.

Proof Of Work 📹

  • Staging
Screenshot 2023-11-10 at 3 37 42 PM
  • Production
Screenshot 2023-11-10 at 3 42 41 PM

@doannimble doannimble changed the title Chore/198 add release note firebase deploy [198] Generate and add "release notes" when distributing new builds on Firebase (staging and production) Sep 25, 2023
@doannimble doannimble self-assigned this Sep 26, 2023
@doannimble doannimble marked this pull request as ready for review September 26, 2023 02:38
@manh-t
Copy link
Contributor

manh-t commented Sep 28, 2023

@doannimble the release note in the PoW contains the last commit message of this PR instead of the title of the PR. I found an issue and commented here. Please kindly check 🙏

Copy link
Member

@luongvo luongvo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@doannimble Please clarify the env usage 🙏

.github/workflows/android_deploy_production.yml Outdated Show resolved Hide resolved
.github/workflows/ios_deploy_staging_to_firebase.yml Outdated Show resolved Hide resolved
@luongvo
Copy link
Member

luongvo commented Oct 4, 2023

@doannimble the release note in the PoW contains the last commit message of this PR instead of the title of the PR. I found an issue and commented here. Please kindly check 🙏

@manh-t Thank you for the great insight 👍

However, I just realized that Firebase will add the default release notes as the merge commit message or the working commit message already.

For example, from my working project:

  • when deploying a build from a merge commit on dev
    image

  • when deploying a build from a working branch on a commit for testing
    image

I doubt the last commit message from your POW comes from the built-in feature of Firebase CLI, not from your effort with the RELEASE_NOTE_CONTENT env, as I don't see its usage anywhere from the workflow 🤔 @doannimble

image

Falling back to the merge commit message or the working commit message in case the command can not get the PR title does not make sense here 💭 What do you think @doannimble @manh-t?

@luongvo luongvo added this to the 1.12.0 milestone Oct 4, 2023
@luongvo
Copy link
Member

luongvo commented Oct 9, 2023

@doannimble please plan to have updates on this PR. Thank you 🤗

@doannimble doannimble temporarily deployed to staging October 9, 2023 02:56 — with GitHub Actions Inactive
@luongvo
Copy link
Member

luongvo commented Oct 11, 2023

@doannimble Do you finish the necessary updates on this PR? Should we mark this PR back to Draft?

@doannimble
Copy link
Contributor Author

@doannimble Do you finish the necessary updates on this PR? Should we mark this PR back to Draft?

@luongvo Yes I do. Please help to review and let me know if we need more improvement 🙏

@manh-t
Copy link
Contributor

manh-t commented Oct 13, 2023

@doannimble we need a new PoW. The current PoW is invalid 🙏

Copy link
Member

@luongvo luongvo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please re-check the script result usage as I don't think it's working properly 🙏

@doannimble doannimble force-pushed the chore/198-add-release-note-firebase-deploy branch from 90697ad to c7f17dc Compare October 27, 2023 08:32
@doannimble doannimble force-pushed the chore/198-add-release-note-firebase-deploy branch 2 times, most recently from a3a89ec to f393785 Compare October 31, 2023 11:28
@doannimble doannimble marked this pull request as ready for review October 31, 2023 11:28
@luongvo luongvo changed the title [198] Generate and add "release notes" when distributing new builds on Firebase (staging and production) [#198] Generate and add "release notes" when distributing new builds on Firebase (staging and production) Nov 1, 2023
Copy link
Member

@luongvo luongvo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks better with https://github.com/8BitJonny/gh-get-current-pr. Please re-check your implementation carefully 🙏

@luongvo
Copy link
Member

luongvo commented Nov 1, 2023

@doannimble I believe we should drop all [Chore] Generate & update sample project commits when rebasing https://github.com/nimblehq/flutter-templates/pull/270/commits 🤓

@doannimble doannimble force-pushed the chore/198-add-release-note-firebase-deploy branch from 348667a to ff16640 Compare November 3, 2023 04:06
@doannimble doannimble force-pushed the chore/198-add-release-note-firebase-deploy branch from b0ef10a to 0b8bb5a Compare November 4, 2023 03:30
Copy link
Member

@luongvo luongvo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update PR description to align to the new approach & POWs for both staging & production 🙏

@luongvo
Copy link
Member

luongvo commented Nov 9, 2023

Please update PR description to align to the new approach & POWs for both staging & production 🙏
@doannimble 🙏

@doannimble doannimble force-pushed the chore/198-add-release-note-firebase-deploy branch from 554fcab to 423b3f1 Compare November 10, 2023 07:19
@doannimble
Copy link
Contributor Author

Please update PR description to align to the new approach & POWs for both staging & production 🙏
@doannimble 🙏

@luongvo Updated 🙏

Copy link
Member

@luongvo luongvo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now all good 👍

Copy link
Contributor

@manh-t manh-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏

@luongvo luongvo merged commit c9f59c1 into develop Nov 13, 2023
@luongvo luongvo deleted the chore/198-add-release-note-firebase-deploy branch November 13, 2023 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Generate and add "release notes" when distributing new builds on Firebase (staging and production)
6 participants