Revamping GitHub Issue workflow #1656
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
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
ankit-db
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
Co-Authored-By: Siddharth Murching <smurching@gmail.com>
smurching
reviewed
Jul 24, 2019
smurching
reviewed
Jul 24, 2019
Co-Authored-By: Siddharth Murching <smurching@gmail.com>
smurching
reviewed
Jul 24, 2019
Co-Authored-By: Siddharth Murching <smurching@gmail.com>
smurching
added
LGTM
rn/none
avflor
pushed a commit
to avflor/mlflow
that referenced
this pull request
Aug 22, 2020
Revamp GitHub issue templates
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.
What changes are proposed in this pull request?
This pull request addresses the due improvements to the issue workflow we have been discussing. It adds a few strict issue templates and adds an issue policy.
How is this patch tested?
N/A
Release Notes
We have updated our GitHub issue policy. Please refer to the policy before filing an issue.
Is this a user-facing change?
Our GitHub issue policy has been updated to streamline the review process and ensure issues are addressed appropriately.
What component(s) does this PR affect?
How should the PR be classified in the release notes? Choose one:
rn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notes