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
Add pull requests info to Test Flight #3948
Conversation
fastlane/Fastfile
Outdated
@@ -180,7 +180,7 @@ platform :ios do | |||
) | |||
end | |||
|
|||
desc "Add a tag for the current build number and push to repo." | |||
desc "Add a release tag for the latest beta and push to repo." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI this is the same description as the next lane on line 192. Could we also add a "This is very similar to..." sentence to one of these to differentiate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated, thanks.
Ignore if this is out of scope, but would it provide more value if we pulled the per merge commit messages into the change messages instead of the PR URL? So for example from: Since we're generally pretty good about naming our PRs, and since the PR number is included, I think it provides more direct value in the release notes without losing the important information and without extra cruft. |
New commit message style:
@staykids - I think this is almost what you asked for. The commit message formatted like |
I made a couple of small changes, but I'm happy to revert in a follow on PR if we need to:
|
@tonisevener Thanks for those. Perfect catch on that testing cod, and thanks for fixing those non-PR merge commits. |
Fixes Phabricator ticket: (N/A, was a request in a meeting)
Notes
Test Steps
Screenshots/Videos
Release notes look like this: