Sitelet https://github.com/flutter/flutter/pull/190324
Skip to content

Update instructions for creating a tooling redirect - #190324

Merged
parlough merged 6 commits into
flutter:masterfrom
parlough:misc/update-use-reliable-links-instructions
Aug 8, 2026
Merged

parlough merged 6 commits into
flutter:masterfrom
parlough:misc/update-use-reliable-links-instructions

Conversation

@parlough

@parlough parlough commented Jul 30, 2026 •

Copy link
Copy Markdown
Member
  • Update the link to the firebase.json to its own short link since the file might move soon.
  • Adjust the prose a bit to account for the flutter/website repository containing multiple websites now.
  • Minor clean up around the doc.

@flutter-dashboard flutter-dashboard Bot added the CICD Run CI/CD label Jul 30, 2026
@github-actions github-actions Bot added c: contributor-productivity Team-specific productivity, code health, technical debt. framework flutter/packages/flutter repository. See also f: labels. d: docs/ flutter/flutter/docs, for contributors labels Jul 30, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation on using reliable links by introducing contractions, clarifying references to the Flutter and Dart website configuration files, and updating the Flutter redirects link to a reliable short link. Feedback was provided to correct a grammatical error where the contraction 'it's' was used instead of the possessive pronoun 'its'.

Comment thread docs/contributing/use-reliable-links.md Outdated
parlough and others added 2 commits July 30, 2026 17:12
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@parlough
parlough requested a review from loic-sharma July 30, 2026 23:25
@loic-sharma

Copy link
Copy Markdown
Member

(Apologies for the late review!)

Drive by question since I didn't know we had docs on these links: do you know when should we use /go/ vs /to/ links? The distinction between these patterns was never fully clear to me :)

@parlough

parlough commented Aug 8, 2026

Copy link
Copy Markdown
Member Author

Thanks for the review!

Drive by question since I didn't know we had docs on these links: do you know when should we use /go/ vs /to/ links? The distinction between these patterns was never fully clear to me :)

That's the goal of this style of links. /go/ should generally be reserved for design docs going forward while /to is for other links that should be kept working. For example those from API docs, the Flutter CLI, or otherwise needed short links such as in videos.

@parlough
parlough enabled auto-merge August 8, 2026 00:53
@parlough parlough added the autosubmit Merge PR when tree becomes green via auto submit App label Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. CICD Run CI/CD d: docs/ flutter/flutter/docs, for contributors framework flutter/packages/flutter repository. See also f: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants