git-workflow/tests
SHA256
16
0
Code Issues 30 Packages Projects Wiki

[STAGING][COMMENT-001] Prevent duplicated comments on subsequent bot runs #68

New Issue
Open
opened 2026-03-04 14:38:04 +01:00 by atartamo · 0 comments
atartamo commented 2026-03-04 14:38:04 +01:00
Owner
Copy Link

Test Steps

  1. Create a package PR.
  2. Wait for the workflow-pr bot to create the related project PR.
  3. Wait for staging-bot to be added as a reviewer and ensure it is listed in the required reviewers for the project PR.
  4. Reduce the bot's polling interval to ensure it runs at least twice during the test.
  5. Mock the OBS result list with a "success" state (e.g., code="succeeded") for all packages, repositories, and architectures.
  6. Let the bot perform its first run.
  7. Wait for the bot to perform a second run without any changes to the PR or OBS results.

Expected Results

  1. After the first run, the staging bot adds the "Build successful" comment.
  2. After the second run, no duplicated "Build successful" comment is added.
**Test Steps** 1. Create a package PR. 2. Wait for the `workflow-pr` bot to create the related project PR. 3. Wait for `staging-bot` to be added as a reviewer and ensure it is listed in the required reviewers for the project PR. 4. Reduce the bot's polling interval to ensure it runs at least twice during the test. 5. Mock the OBS result list with a "success" state (e.g., `code="succeeded"`) for all packages, repositories, and architectures. 6. Let the bot perform its first run. 7. Wait for the bot to perform a second run without any changes to the PR or OBS results. **Expected Results** 1. After the first run, the staging bot adds the "Build successful" comment. 2. After the second run, no duplicated "Build successful" comment is added.
atartamo added the
bot
staging
status
todo
 labels 2026-03-04 14:38:04 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority
High
Priority
Medium
bot
staging
bot
workflow-pr
not-implemented
status
done
status
in-progress
status
todo
No Label
bot
staging
status
todo
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
M0ses adamm adrianSuSE andriinikitin atartamo bigironman dancermak darix dirkmueller dmach eroca jdsn jzerebecki mstrigl oertel smithfarm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: git-workflow/tests#68
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?