Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Label > Trigger/Phase Configuration #64

Closed
rootelement opened this issue Aug 28, 2018 · 2 comments
Closed

Label > Trigger/Phase Configuration #64

rootelement opened this issue Aug 28, 2018 · 2 comments
Labels
enhancement New feature or request P5 Nice to have but non-critical

Comments

@rootelement
Copy link

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:

  1. Prefix labels for this with something (ie: TCX-Assigned)
    1. Allow the prefix to be configured when the repo/project is set up
  2. Allow a Label > Action mapping configuration for the user when they set up the repo
@cwdcwd cwdcwd added enhancement New feature or request P5 Nice to have but non-critical labels Aug 28, 2018
@jmgasper
Copy link
Collaborator

  1. We are currently implementing a tcx_ prefix. Prefix labels with tcx_ #47

  2. 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?

@rootelement
Copy link
Author

  1. 👍
  2. Use case being:
    https://github.com/ConsenSys/mythril/issues

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.

This can be closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request P5 Nice to have but non-critical
Projects
None yet
Development

No branches or pull requests

3 participants