docs: update release process documentation. #8529
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Salakar
reviewed
Apr 27, 2022
CONTRIBUTING.md
Outdated
| 10)Update the documentation by manually triggering the [publish docs workflow](https://github.com/FirebaseExtended/flutterfire/actions/workflows/docs.yaml);  | ||
|
|
||
| 7) After successful dry run, commit all changes with the signature "chore(release): prepare for release". | ||
| 8) Run `git push origin master` & open pull request for review on GitHub. |
Member
There was a problem hiding this comment.
Shouldn't be git push origin master here - we're pushing the new release/* branch instead
Salakar
reviewed
Apr 27, 2022
Co-authored-by: Mike Diarmid <[email protected]>
Salakar
approved these changes
May 3, 2022
Ehesp
approved these changes
May 3, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Description
See title.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]).This will ensure a smooth and quick review process. Updating the
pubspec.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?