kbendick opened a new issue #1277:
URL: https://github.com/apache/iceberg/issues/1277


   As the number of subprojects grows and as the number of committers and 
contributors grows, it will likely become more and more difficult to find PRs 
that are associated with certain subproject (e.g., if I wanted to look at PRs 
prooosing changes for `iceberg-core` or for `flink`).
   
   It would be entirely possible to use a github action to place tags on each 
PR automatically that mentions the relevant affected subprojects.
   
   This way, contributors could find the PRs that are most relevant to the work 
that they're doing.
   
   I'm not sure if the ASF has infrastructure in place that they prefer to use 
over github actions. However, for public projects, github actions are free so I 
don't see the harm in using them personally. Additionally, given it's the ASF, 
there is definitely infra in place for running certain automated tasks. 
However, I'm not sure if tagging PRs is possible outside of github actions. And 
it would after all be free for us as we're an OSS project.
   
   Do people feel there would be benefit in having this? It wouldn't 
necessarily help locate PRs for say, spark streaming vs spark batch, but it 
would at least help identify PRs without requiring the contributor to mark 
`Flink` or `Spark3 Runtime` in their PR titles.
   
   I'm open to hearing what others have to say before committing to adding 
this. I personally think it would help triage PRs more effectively, especially 
for heavy contributors / PMCs who likely have to remember many different 
subprojects they've promised to take a look at in "the next few days" ™️  😄 
   
   For pricing info, see the section marked `Simple, pay-as-you-go pricing`. 
But tldr: it's free. https://github.com/features/actions


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to