getting-started: register-device: add tag parameter for first target #860
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.
Previously, our "fast first target" artifacts were built from the "main" branch of the LmP and would auto-register using the "main" tag.
With the latest changes to our LmP workflow, we now have LTS branch names such as "scarthgap" and also a "main" branch representing upstream Yocto / OE development.
The artifacts used for LmP version releases will most likely come from an LTS branch, and will attempt to register using that branch name by default (IE: "scarthgap" tag).
The device should be registered to follow the "main" tag to match the 2nd target of a newly created Factory. So let's add the "-t main" parameter to our docs.
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness
Overview
Why merge this PR? What does it solve?
Checklist
make linkcheck.-s, --signoff).-S, --gpg-sign).Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.