Skip to content

GH action to update submodule#26

Merged
donald-pinckney merged 1 commit intomainfrom
donald/dev-updating-main
Apr 1, 2026
Merged

GH action to update submodule#26
donald-pinckney merged 1 commit intomainfrom
donald/dev-updating-main

Conversation

@donald-pinckney
Copy link
Copy Markdown
Collaborator

What was changed

Adds a GH action which bumps the skill submodule pointer to the latest SHA, and pushes a commit doing so. This only changes the dev branch of agent-skills, and only uses SHAs from the dev branch of skill-temporal-developer.

Why?

It is quite annoying to manually make submodule updating commits, and at least for the dev branches we do always want them to be in sync.

Checklist

  1. Closes

  2. How was this tested:
    Will have to test after merging.

  3. Any docs updates needed?
    No

@donald-pinckney donald-pinckney requested a review from a team as a code owner April 1, 2026 16:40
@donald-pinckney donald-pinckney merged commit de6c169 into main Apr 1, 2026
3 checks passed
@donald-pinckney donald-pinckney deleted the donald/dev-updating-main branch April 1, 2026 16:42
Comment on lines +14 to +47
runs-on: ubuntu-latest
steps:
- name: Checkout dev branch
uses: actions/checkout@v4
with:
ref: dev
submodules: true
# Use default GITHUB_TOKEN — has push access to the repo
token: ${{ secrets.GITHUB_TOKEN }}

- name: Update submodule to latest dev
run: |
cd plugins/temporal-developer/skills/temporal-developer
git fetch origin dev
git checkout origin/dev
cd "$GITHUB_WORKSPACE"

- name: Check for changes
id: check
run: |
if git diff --quiet; then
echo "changed=false" >> "$GITHUB_OUTPUT"
else
echo "changed=true" >> "$GITHUB_OUTPUT"
fi

- name: Commit and push
if: steps.check.outputs.changed == 'true'
run: |
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
git add plugins/temporal-developer/skills/temporal-developer
git commit -m "update submodule to latest dev"
git push origin dev
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Semgrep identified an issue in your code:
No explicit GITHUB_TOKEN permissions found at the workflow or job level. Add a permissions: block at the workflow root (applies to all jobs) or per job with least privilege (e.g., contents: read and only specific writes like pull-requests: write if needed).

To resolve this comment:

🔧 No guidance has been designated for this issue. Fix according to your organization's approved methods.

💬 Ignore this finding

Reply with Semgrep commands to ignore this finding.

  • /fp <comment> for false positive
  • /ar <comment> for acceptable risk
  • /other <comment> for all other reasons

Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by missing-explicit-permissions.

You can view more details about this finding in the Semgrep AppSec Platform.

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.

1 participant