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
{{ message }}
This repository was archived by the owner on Mar 13, 2025. It is now read-only.
I know for Consensys, we came in to a living, breathing git repo. I could see labels getting very muddy, and possibly be a barrier to entry for us ramping up on a project.
Just a suggestion, either:
Prefix labels for this with something (ie: TCX-Assigned)
Allow the prefix to be configured when the repo/project is set up
Allow a Label > Action mapping configuration for the user when they set up the repo
The text was updated successfully, but these errors were encountered:
Do we need a mapping? I'm concerned about that just being one more configuration "knob" to tweak, but I'm not seeing much potential benefit. What would be a normal use case for changing the mapping?
We came into this living project with open issues. I'm thinking if they already have a format for the stages, that we could tweak our labels to fit their nomenclature. For example, if someone had an "Assigned" tag already. But If you're implementing the tcx_ prefix, I think that'll be fine.
I know for Consensys, we came in to a living, breathing git repo. I could see labels getting very muddy, and possibly be a barrier to entry for us ramping up on a project.
Just a suggestion, either:
The text was updated successfully, but these errors were encountered: