Add "Phase 0" issue template for when partnerships need engineering input into new hub deployments #4921
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
…ub refinement is required
for more information, see https://pre-commit.ci
|
I'm seeing the error "There is a problem with this template Body must contain at least one non-markdown field. Learn more about this error." when trying to use this new template. |
|
Oh, boo. Really I wanted just a markdown template, but then I couldn't automatically assign it to the project. I'll fix it tomorrow. |
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.
Occasionally, some sync discussions between partnerships and engineering still need to happen in order to fully refine the new hub deployment issues. This new issue template represents a mechanism by which partnerships can request that discussion in a way that is visible on the engineering board.
This is a short term bridge while we develop other resources to help communities and partnerships make these decisions from our "canned" product list without engineering input. Such resources will likely include improved community-facing documentation about our feature set, sales engineering runbooks, etc.