fix: make pstack changelog sync resilient to missed commits#5
Merged
Conversation
Co-Authored-By: Florin <[email protected]>
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.
Summary
Makes the weekly pstack changelog sync robust against missed commits without changing the workflow schedule.
sync-pstack.pynow paginates through up to 100 pages (up from 2) and uses thesincetimestamp of the latest entry, so it still catches new history if the last recorded SHA is rebased or no longer on the branch.sinceinstead of silently truncating at the page limit.sync-pstack.ymlnow captures the script output to the workflow step summary and flags warnings, so missed-commit cases are visible in the Actions run.Trigger behavior is unchanged: still runs every Monday at 09:00 UTC and on
workflow_dispatch.Link to Devin session: https://app.devin.ai/sessions/041012c8528a46e2955cb099dd3b4eb4
Requested by: @HustleCoding