Skip to content

Conversation

@mike-scott
Copy link
Contributor

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

  • Merge (pending reviews)
  • Merge after date or event
  • Draft

Overview

Why merge this PR? What does it solve?

Checklist

  • Run spelling and grammar check, preferably with linter.
  • Avoid changing any header associated with a link/reference.
  • Step through instructions (or ask someone to do so).
  • Review for wordiness
  • Match tone and style of page/section.
  • Run make linkcheck.
  • View HTML in a browser to check rendering.
  • Use semantic newlines.
  • follow best practices for commits.
    • Descriptive title written in the imperative.
    • Include brief overview of QA steps taken.
    • Mention any related issues numbers.
    • End message with sign off/DCO line (-s, --signoff).
    • Sign commit with your gpg key (-S, --gpg-sign).
    • Squash commits if needed.
  • Request PR review by a technical writer and at least one peer.

Comments

Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

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.

Signed-off-by: Michael Scott <mike@foundries.io>
@mike-scott mike-scott requested a review from kprosise September 26, 2025 21:46
@mike-scott mike-scott self-assigned this Sep 26, 2025
Copy link
Contributor

@kprosise kprosise left a comment

Choose a reason for hiding this comment

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

Lgtm

@kprosise kprosise merged commit 2179d11 into foundriesio:main Sep 26, 2025
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants