ansible-collections/git-events
2
0
Fork 0
Code Issues 1 Pull Requests Actions Projects Releases Wiki Activity

When nothing found review is still made and denied #5

New Issue
Closed
opened 2025-07-11 12:04:09 +00:00 by jon · 0 comments
jon commented 2025-07-11 12:04:09 +00:00
Owner
Copy Link

when the problem matcher runs there is still a review posted requesting changes when there is nothing found.

Details

Update the problem matcher to do the following:

  • Dont post as requesting changes
  • Dont post comment
  • if review already exists, mark as "approved"
  • if no review already exists, do nothing
when the problem matcher runs there is still a review posted requesting changes when there is nothing found. ## Details Update the problem matcher to do the following: - [x] Dont post as requesting changes - [x] Dont post comment - [x] if review already exists, mark as "approved" - [x] if no review already exists, do nothing
jon added spent time 1 minute 2025-07-12 09:25:08 +00:00
jon self-assigned this 2025-07-12 09:25:13 +00:00
jon closed this issue 2025-07-12 14:11:41 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Area/CI-CD
Documentation changes
Area/Documentation
Documentation changes
Area/Security
This is security issue
Area/Testing
Issue or pull request related to testing
Bug
Failure to Confirm
Bug exists due to not confirming/testing code
Bug
Regression
THe bug is a regression of a feature
Bug
To be Confirmed
This bug is not confirmed
Bug
Unable to Reproduce
A developer can not re-create/re-produce the bug
Compat/Breaking
Breaking change that won't be backward compatible
Impact
Critical
1
The impact is critical in that it is blocking or prevents usage.
Impact
High
2
The impact requires that changes be made for continuted usage.
Impact
Low
4
The impact requires the user approach from a different angle for continued usage.
Impact
Medium
3
The impact requires a workaround for continued usage.
Impact
Very Low
5
The impact has a slight effect on usage.
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Priority
Very High
1
The priority is critical
Priority
Very Low
5
The priority is very low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Type
Bug
Something is not working
Type
Epic
Epic User Story
Type
Feature
Feature / Module
Type
Incident
Something occured related to a service
Type
RFE
Request for Enhancement
Type
Task
A work item that must be done
Urgency
Low
4
Prioritize this amoungst your list of things to do.
Urgency
Major
1
Urgency is so high it should have been dealt with last week.
Urgency
Medium
3
Start as soon as possible.
Urgency
Very High
2
Urgency is high enough to warrant near immediate commencement.
Urgency
Very Low
5
Add this to your list of things to do.
No Label
Bug
Failure to Confirm
Impact
Very Low
5
Priority
Medium
3
Type
Bug
Urgency
Very High
2
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason jon
No Assignees jon
1 Participants
Notifications
Total Time Spent: 1 minute
jon
1 minute
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ansible-collections/git-events#5
No description provided.
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?