Fix prototype_build_details_comment
action when used outside FAD context
#642
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
While working on updating Tumblr-Android to use the latest
release-toolkit
version13.0.0
(internal ref: Tumblr/android#24388), I noticed that the PR comment for the Prototype Build (which uses direct download from S3 and does not use Firebase App Distribution) contained extra rows.Notice the
Build Number
andVersion
rows in the table. TheApplication ID
is not empty even if this Prototype Build didn't use FAD, because we happen to provide the value for this metadata explicitly though.This PR used TDD to fix the issue:
Checklist before requesting a review
bundle exec rubocop
to test for code style violations and recommendations.specs/*_spec.rb
) if applicable.bundle exec rspec
to run the whole test suite and ensure all your tests pass.CHANGELOG.md
file to describe your changes under the appropriate existing###
subsection of the existing## Trunk
section.If applicable, add an entry in theMIGRATION.md
file to describe how the changes will affect the migration from the previous major version and what the clients will need to change and consider.