Document GCS Azure DevOps localization bug-tracking process#40668
Open
benhillis wants to merge 6 commits into
Open
Document GCS Azure DevOps localization bug-tracking process#40668benhillis wants to merge 6 commits into
benhillis wants to merge 6 commits into
Conversation
Community localization PRs (Resources.resw edits and new locale files) are reviewed/incorporated by the Microsoft GCS localization pipeline via Azure DevOps Bug work items, not merged directly from GitHub. This adds a guide covering the ADO project coordinates, the Bug work-item template, required custom fields with known-good values, the Custom.Language picklist mapping, the az boards workflow, and the az.cmd/permission gotchas. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This documentation-only PR records the process for routing community localization PRs through the GCS Azure DevOps bug-tracking workflow instead of merging translated resources directly from GitHub.
Changes:
- Adds a new Copilot-facing guide for creating GCS localization tracking bugs.
- Documents required Azure DevOps fields, language picklist lookup, CLI creation flow, and common gotchas.
- Adds a localization-section reference from the repository Copilot instructions.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/copilot/localization-bugs.md |
New guide describing the GCS Azure DevOps workflow for community localization PRs. |
.github/copilot-instructions.md |
Adds a pointer to the new localization bug-tracking guide. |
Area-path-scoped permissions: the working path is 'C and AI\Unspecified', not the project root. Also note System.Description is required alongside ReproSteps, and add the tr-TR language mapping. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Bugs filed under 'C and AI\Unspecified' get cleaned up and that access is not stable. The correct, durable path for WSL localization bugs is 'Global\Windows', confirmed against existing manually-filed WSL loc bugs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Capture the hard-won lessons from filing these bugs: - 'not found' from WIQL/GET often means no read access, not deletion; a gap in sequential IDs means items were created but are now invisible - always read the bug back after creating to confirm it persisted - set UTF-8 console encoding for non-ASCII locale content, and don't pipe az output straight into ConvertFrom-Json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Localized Resources.resw files (everything except en-US) are generated by the third-party GCS localization team and regenerated downstream, so any translation edits made in a GitHub PR get overwritten and cannot be merged. - CONTRIBUTING.md: tell contributors to file an issue for translation problems instead of opening a PR. - copilot-instructions.md + localization-bugs.md: when triaging, look for BOTH issues and PRs and file a tracking Bug for each; decline loc PRs with a pointer to the contributing guidance. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Localized content lives in two families, both generated by the GCS loc team and regenerated downstream: per-locale UI strings (localization/strings/<locale>/Resources.resw) and per-locale Intune/ group-policy templates (intune/<locale>/WSL.adml). Only the en-US sources and the language-neutral intune/WSL.admx originate in this repo. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
|
||
| ### After creating | ||
|
|
||
| Cross-link the systems: paste the ADO Bug ID into the GitHub PR (and vice-versa) so reviewers can find both. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of the Pull Request
Adds documentation for how community localization PRs are tracked in the GCS Azure DevOps project, since they are reviewed/incorporated by the Microsoft localization pipeline rather than merged directly from GitHub.
PR Checklist
.github/copilot/localization-bugs.mdand referenced it from.github/copilot-instructions.mdDetailed Description of the Pull Request / Additional comments
New guide
.github/copilot/localization-bugs.mdcaptures:GCS_Agileprocess, Bug work-item template link)Custom.Languagepicklist mapping (e.g.es-ES->Spanish (Spain, International Sort)) and how to list allowed valuesaz boards work-item createcommand and suggested description bodyaz.cmdtruncating URLs at&(use the Accept header forapi-version), and the create-permission requirement (probe withvalidateOnly=true, fall back to the web template)Follows the existing
.github/copilot/convention (commit.md,review.md,test.md).Note
Field values were reverse-engineered from the live project; once a bug is filed from the template with a permitted identity, the prefilled values should be diffed against this doc and corrected if needed.
Validation Steps Performed
Custom.Languagepicklist values and required-field set against the live GCS project viaaz rest.