ci: support stacked PRs in docs update cron job#3779
Merged
ComputelessComputer merged 1 commit intomainfrom Feb 9, 2026
Merged
ci: support stacked PRs in docs update cron job#3779ComputelessComputer merged 1 commit intomainfrom
ComputelessComputer merged 1 commit intomainfrom
Conversation
Co-Authored-By: john@hyprnote.com <john@hyprnote.com>
✅ Deploy Preview for hyprnote-storybook canceled.
|
✅ Deploy Preview for hyprnote canceled.
|
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
ci: support stacked PRs in docs update cron job
Summary
Updates the
devin_update_docscron workflow so that when an open docs update PR already exists from a previous run, the next Devin session is instructed to stack its PR on top of the existing one (branching from it and targeting it as base) instead of creating a separate PR againstmain.A new "Find existing docs update PR" step uses
gh pr listto search for open PRs authored byapp/devin-ai-integrationwhose title matchesdocs.*update|update.*docsand branch starts withdevin/. If found, the branch name and PR number are passed into the Devin prompt via Jinja2 template variables.Also closed two outdated docs update PRs (#3674, #3615) that were stale from previous cron runs.
Review & Testing Checklist for Human
jqfilter logic:sort_by(.number) | last // empty— confirm this correctly picks the most recent PR and that// emptyproduces an empty string (not"null") when no matchif [ -n "$DOCS_PR" ] && [ "$DOCS_PR" != "null" ]handles both the empty-string and JSON-null cases correctlydocs.*update|update.*docs— consider whether it's too broad (could match unrelated PRs) or too narrow (could miss legitimate docs cron PRs). May want to filter by tagdocs_updateinstead if the Devin API tags PRsworkflow_dispatchrun to test end-to-end with and without an existing open PRNotes