Skip to content

Conversation

@russellwheatley
Copy link
Member

Description

See title.

Related Issues

none.

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.yaml and changelogs is not required.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

@github-actions
Copy link

github-actions bot commented Apr 12, 2022

Visit the preview URL for this PR (updated for commit 830a0fe):

https://flutter-firebase-docs--pr8448-russell-docs-improv-sr5krjjd.web.app

(expires Wed, 20 Apr 2022 12:18:08 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

@russellwheatley russellwheatley changed the title docs: Update FlutterFire cli documentation. docs: Update FlutterFire CLI documentation. Apr 12, 2022
@Salakar Salakar changed the title docs: Update FlutterFire CLI documentation. docs: update documentation to support latest CLI release. Apr 13, 2022
@Salakar Salakar merged commit 6da2317 into master Apr 13, 2022
@Salakar Salakar deleted the @russell/docs-improve branch April 13, 2022 12:31
@firebase firebase locked and limited conversation to collaborators May 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants