You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RDKEMW-15981: ci - onboard sync-develop-to-main automation (1.1.2) - #492
The previously committed bundle on this branch was built locally with
an ad hoc version string (1.2.0) that was never an actual published
release and predates the actions-v1.1.0 fixes (fallback PR branches
keyed by source commit, stale fallback PR cleanup, GITHUB_TOKEN
limitation docs). Replace it with the officially released
actions-v1.1.0 bundle from rdk-e/app-gateway-automation.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
brendanobra
changed the title
RDKEMW-15981: ci - onboard sync-develop-to-main automation (1.2.0)
RDKEMW-15981: ci - onboard sync-develop-to-main automation (1.1.0)
Oct 12, 2026
Fixes the fallback issue manual-merge checklist, which previously told
responders to merge source_branch into the fallback branch (a no-op
since the fallback branch is created directly from that source
commit). It now correctly instructs merging target_branch instead.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
brendanobra
changed the title
RDKEMW-15981: ci - onboard sync-develop-to-main automation (1.1.0)
RDKEMW-15981: ci - onboard sync-develop-to-main automation (1.1.1)
Oct 12, 2026
Any value other than true, 1, or yes currently disables failure, so a typo such as ture makes a merge-conflict run succeed despite the safety-oriented default. Accept only the documented true/false values (or fail closed on unknown values) before deciding the exit status.
This issue also appears on line 622 of the same file.
Handle missing option value before dereferencing $2
Invoking the documented option without a value dereferences $2 under set -u, producing an unhelpful unbound variable failure instead of the usage error below. Check that a non-empty second argument exists before assigning VERSION, and reject the malformed invocation explicitly.
Drops --force from the label-ensure step's gh label create call so
re-running the fallback path no longer overwrites an existing label's
color/description; the trailing || true still treats non-existence as
non-fatal.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
brendanobra
changed the title
RDKEMW-15981: ci - onboard sync-develop-to-main automation (1.1.1)
RDKEMW-15981: ci - onboard sync-develop-to-main automation (1.1.2)
Oct 13, 2026
Publish workspace path before fallible setup commands
.github/actions/sync-branches/action.yml:146
Publish path immediately after mktemp -d. If clone, checkout, or remote setup fails before line 146, the always-running cleanup step receives no workspace path and leaves this directory behind; this accumulates repository data on the self-hosted runner used by the reference template. Reordering the output before the fallible commands lets cleanup remove partial workspaces; regenerate the lock hash afterward.
Apply labels and reviewers when updating existing fallback PRs
.github/actions/sync-branches/action.yml:379
Retries for the same source SHA take this branch and exit after changing only the title/body, so pr_labels and assign_reviewers are never applied to an existing fallback PR. A configuration change—or a manually removed label—therefore has no effect even though the action advertises updating fallback PRs. Build the edit command with --add-label and --add-reviewer from the two inputs before returning, then regenerate the managed-file hash in the lock file.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
4 participants
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.
![github-actions[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
brendanobra
changed the title
Description
What does this PR change/fix and why?
If there is a corresponding JIRA ticket, please ensure it is in the title of the PR.
Test Procedure
How to test this PR (if applicable)
Type of Change
Automation fo manual process (merge develop -> main)
Requires Bitbake Recipe changes?
meta-rdk-ext/recipes-containers/dobby/dobby.bb) must be modified to support the changes in this PR (beyond updatingSRC_REV)