chore: Separate workflow to add/remove 'stale' label

[totoprayogo1916]

Description
Follow-up #7957

Checklist:

• Securely signed commits

[kenjis]

Not sure if it would work without the cronjob.
But let's merge and see.

[kenjis]

#7986 has conflict, but not labeled.

[totoprayogo1916]

#7986 has conflict, but not labeled.

When #7986 conflicts, is there a push on the develop or 4.x branch?

[totoprayogo1916]

Or maybe a commit on the PR shows it's still a conflict.

I want to see where the job action has been going.

[kenjis]

When #7986 conflicts, is there a push on the develop or 4.x branch?

Yes. #7967 was merged.
And the action is: https://github.com/codeigniter4/CodeIgniter4/actions/runs/6332904494/job/17200180659

[totoprayogo1916]

The "mergeable" value is UNKNOWN

[kenjis]

Yes.

And now I got my PRs (#7955, #7981) to be labeled after merging #7990

[kenjis]

The value of the mergeable attribute can be true, false, or null. If the value is null, then GitHub has started a background job to compute the mergeability. After giving the job time to complete, resubmit the request. When the job finishes, you will see a non-null value for the mergeable attribute in the response. If mergeable is true, then merge_commit_sha will be the SHA of the test merge commit.
https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#get-a-pull-request

The first merge returns UNKNOWN and then the value is determined.
So the next merge will return CONFLICTING and put the label.

[totoprayogo1916]

The first merge returns UNKNOWN and then the value is determined.
So the next merge will return CONFLICT and put the label.

It's not always going to be of real value,
#6845 conflict has the value UNKNOWN, but in some jobs it is appropriate.

[ddevsr]

I testing with schedule as already suggested by @totoprayogo1916, always revalidate limitable latest PR by get latest status mergeable when schedule running.

https://github.com/PHPDevsr/check-conflict-action/actions
https://github.com/PHPDevsr/playground/actions

[kenjis]

I think "Run at every 6 minutes" is running too often.

In the case of UNKNOWN, I think if we wait some seconds before retrieving again, we can get the result.

[kenjis]

Check Conflicts Remove label failed.
See #7992

[ddevsr]

Before conflict https://github.com/codeigniter4/CodeIgniter4/actions/runs/6309422686/job/17129306013 success running with read permission because no have label stale to remove using write permission. And after conflict bot trigger added label and comment using. Many action running using permission read, I think this section of permission job.

https://github.com/PHPDevsr/check-conflict-action/actions
https://github.com/PHPDevsr/playground/actions

You can see 2 action running well with write permission

[kenjis]

@ddevsr Sorry, I don't get what you say.
If you can fix the issue, please send a PR.

[totoprayogo1916]

I think "Run at every 6 minutes" is running too often.

In the case of UNKNOWN, I think if we wait some seconds before retrieving again, we can get the result.

If only we could execute this action at the end instead of others.

[kenjis]

Removed label-add-remove-conflict-single-pr.yml, because it does not work at all.
See #7999