Bidirectional sync between project board columns and labels about core

[VannTen]

@harshad16 Could we pull that into the devsecops project ? Feels relevant.

[sesheta]

@VannTen: This issue is currently awaiting triage.
If a refinement session determines this is a relevant issue, it will accept the issue by applying the
triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[VannTen]

/sig devsecops

[goern]

sounds helpful, could you put an hour or so in and figure out if we can do it easily for our repos and https://github.com/orgs/open-services-group/projects/21/views/1

@schwesig

[VannTen]

Ok, I'll take a look.

[VannTen]

So, not that easy it would seem. From the github docs (workflows do not support org projects)[ https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#project_card] (third note). Beside, I've seen several projects doing one of the sync direction, but not both. So that would need at least some work. I've not checked the new API for beta projects, but it might be relevant. Related #424 /triage needs-information

[VannTen]

Gitlab has issue
boards which do
exactly that.

Regarding the new project version, they don't appear to provide that
functionality either. (might be in the API, but managing that ourselves seems
more trouble than it's worth)

[codificat]

An earlier attempt to implement this using prow: thoth-station/thoth-application#2450

This was only uni-directional (auto-add issues to project boards), and it's not really working though. Oh, and it is only meant to work with the "classic" projects, not the new ones.

[VannTen]

Uni-directional meant everyone has to use the same process, though. It would certainly be simpler (as mentioned earlier, several github actions do just that). I'll be fine with working only with labels as I'd rather use gh than the github UI, but I'm not sure everyone is a fan^. Also, if we do decide that everyone should use one workflow, we should disable (with permissions or settings or whatever) the other, otherwise it will be used anyway ^. ||| Maybe I should reframe this issue -> 'Uniform SIG assignations triage process & automation' or something like that. EDIT: Can't do md in email reply. Wow, that's ... disappointing

[sesheta]

Issues needing reporter input close after 60d,

If there is new input, reopen with /reopen.