Skip to content

Fix rejection handling of submissions#10127

Open
seanbudd wants to merge 9 commits into
masterfrom
fixRejection
Open

Fix rejection handling of submissions#10127
seanbudd wants to merge 9 commits into
masterfrom
fixRejection

Conversation

@seanbudd

@seanbudd seanbudd commented Jul 9, 2026

Copy link
Copy Markdown
Member

Tested here: seanbudd#33
Fixup of #9877
Should close #10139

This pull request makes several improvements to the GitHub Actions workflow for add-on metadata submission, focusing on better automation, more robust handling of manual review rejections, and minor documentation and data updates. The most significant changes include refactoring how rejection reasons are fetched and posted, improving branch and PR management, and clarifying the submission review process.

Fixed AI slop that snuck into poorly tested previous PR:

  • Refactored the manual review rejection step in .github/workflows/checkAndSubmitAddonMetadata.yml to use a shell script with gh api and jq for fetching rejection reasons and reviewers, replacing the previous actions/github-script JavaScript approach. This makes the process more transparent and easier to debug.
  • Improved branch and PR management by updating the PR closing step to use gh pr close ... --delete-branch, ensuring the branch is deleted remotely, and by adding a git push before merging to guarantee the branch is up to date. Added a short delay before merging to avoid race conditions. [1] [2]

@seanbudd seanbudd requested a review from a team as a code owner July 9, 2026 08:45
@seanbudd seanbudd requested review from SaschaCowley and Copilot and removed request for a team July 9, 2026 08:45
Comment thread submitters.json Outdated
@seanbudd seanbudd marked this pull request as draft July 9, 2026 08:46

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR adjusts the add-on submission automation to better handle manual-review rejections (including fetching and posting rejection reasons) and makes minor supporting documentation/data updates.

Changes:

  • Refactors the manual-review rejection handling in checkAndSubmitAddonMetadata.yml to use gh api + jq and closes PRs with --delete-branch.
  • Adds a pre-merge git push and a short delay to reduce merge race conditions.
  • Updates reviewer documentation and a submitter entry.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
submitters.json Removes trustedSubmitter for one submitter entry.
docs/dev/submissionReview.md Clarifies what reviewers should do when unsure during submitter review.
.github/workflows/checkAndSubmitAddonMetadata.yml Refactors rejection-reason retrieval and improves PR/branch management around rejection + merge.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/checkAndSubmitAddonMetadata.yml Outdated
@seanbudd seanbudd marked this pull request as ready for review July 9, 2026 23:37
Comment thread submitters.json Outdated
Signed-off-by: Sean Budd <seanbudd123@gmail.com>
Comment on lines +204 to +208
# checkout of repo needed for posting comments to issues
- name: Checkout repository
uses: actions/checkout@v6
with:
ref: ${{ env.branchName }}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Wouldn't it be more efficient to leave the checkout until after this check, and in "Warn if VT not set up correctly" do

gh -R "${{ github.repository }}" issue comment "${{ inputs.issueNumber }}" --body-file vt-not-set-up-correctly.md

Comment on lines +531 to +532
# wait for a few seconds to ensure the PR is up to date before merging
sleep 3

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why is this necessary? git push is synchronous. This also seems very fragile.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I was hoping this would fix whatever is causing #10139

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants