GitHub labels llvm:binary-utilities and tools:llvm-objcopy/strip

Project Infrastructure GitHub
1

Hello,

I’d like to clarify usage of two labels: llvm:binary-utilities and llvm-objcopy/strip.

Recently I’ve created two PRs relevant to llvm-objcopy/strip. And I saw that llvmbot automatically applied label llvm:binary-utilities:

To keep labels consistent I applied llvm:binary-utilities to the relevant issue. However after a while one of maintainers removed this label from the issue, but not from the pull-request.

It seems to me that there is inconsistency with these labels, and the process could be improved. Or is it okay that an issue and its PR do not have the same labels?

From my experience with other projects, labels in the issue and pull-request/merge-request are keeped in sync using a bot.

cc @EugeneZelenko

2

Since issues are clearly in llvm-objcopy, I think llvm-objcopy/strip label is best fit for them. Why additional label is needed? Bot tend to add redundant labels to pull requests.

3

binary-utilities is a catch-all for all LLVM binary utilities. As we have the llvm-objcopy/strip label, we probably don’t need the binary-utilities label to cover stuff that is covered by the other label. At the same time, llvm-objcopy and llvm-strip are binary utilities, so it’s not wrong for it to be applied to them. In other words, I don’t think in the future the additional label needs removing necessarily.