You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix labeler + automaticaly add to GH project (#4037)
* add new way to check permissions
* align with android repo
* add workflow dispatch
* disable add label
* restove project assignment
* add to project board
* try to set agent
* remove condition on PR
* provide gh token
* first working draft
* use test PR URL
* remove test PR url and make it ready for use
* restore java-agent label
* use hardcoded issue ID
* use issue-labeler
* remove warning for unused config option
* restore it
* try to reuse common code
* try to fix token
* reuse set status
* fix test url
* try to set agent field
* try to set iteration
* cleanup, still not ready for prime-time
* switch to project numeric ID
* use new parameters format
* try to set previous
* try with next
* use iteration name
* restore conditions in labeler workflow
* use elastic version
* simplify and avoid issue-labeler
* cleanup
* another cleanup
* add missing NUMBER and GH_TOKEN
* simplify use the PR url
👋 @{{ author }} Thanks a lot for your contribution!
66
-
67
-
It may take some time before we review a PR, so even if you don’t see activity for some time, it **does not** mean that we have forgotten about it.
68
-
69
-
Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming [milestone](https://github.com/elastic/apm-agent-java/milestones). The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it.
70
-
- name: Assign new internal pull requests to project
0 commit comments