Add area/configuration label #8665
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There's a considerable amount of work done on Galaxy's configuration system, from definition in the schema to loading and processing configuration options, to handling configuration files. Currently, there is no easy way to tag this: the "area" label that has been used is "admin", but I don't think that's correct: modifying how configuration is processed by the system is very different from how it is utilized by the user. I realize that would add yet another option when tagging an issue or PR, but I think the benefit of accurately tagging that work outweighs a little bit of added complexity. I'll be happy to retag relevant issues and PRs (for the past several months or even 2019, maybe?) if this is approved.
martenson
approved these changes
Sep 18, 2019
|
@ic4f it could be useful to retroactively label the recently merged configuration PRs |
|
Thank you! |
|
Splendid! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's a considerable amount of work done on Galaxy's configuration
system, from definition in the schema to loading and processing
configuration options, to handling configuration files. Currently, there
is no easy way to tag this: the "area" label that has been used is
"admin", but I don't think that's correct: modifying how configuration
is processed by the system is very different from how it is utilized by
the user.
I realize that would add yet another option when tagging an issue or PR,
but I think the benefit of accurately tagging that work outweighs a
little bit of added complexity. I'll be happy to retag relevant issues and
PRs (for the past several months or even 2019, maybe?) if this is approved.