Make the file a yaml file and change:
1) Refer to the new "Known issues" project.
2) Update the version to command to be "flutter --version" instead of "dart --version".
3) Include code sample and repro instruction inputs.
Change-Id: Ia655d860cc5547097a292101a92439109916bee0
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/409204
Reviewed-by: Kevin Moore <kevmoo@google.com>
Commit-Queue: Nate Biggs <natebiggs@google.com>
This is a temporary template that we will use to capture feedback for stateful hot reload on the web.
Once hot reload is fully enabled and it is in a stable state, we will remove this template and any further issues discovered in the future will be filed via the normal Web issue filing template.
Change-Id: I462cb20898953f08335010f383574096315078c8
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/409020
Reviewed-by: Kevin Moore <kevmoo@google.com>
Commit-Queue: Nate Biggs <natebiggs@google.com>
Add a `config.yml` which includes a stack overflow link as "contact" to
encourage general help questions to get help from the community first.
Enable blank issues because they are currently allowed.
Change-Id: Ifc43e36cd022a0eafa6208f26eb618e1a27c791c
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/397100
Auto-Submit: Nate Bosch <nbosch@google.com>
Reviewed-by: Devon Carew <devoncarew@google.com>
Commit-Queue: Nate Bosch <nbosch@google.com>
Clarify the same CP request can be used for both beta and stable and
make more room for doing so, as well as including a whole list of
changelists to be cherry-picked for complicated cases. Clarify distinct
gerrit CLs are needed for beta and stable.
Replace the informationless risk field that everyone says is low with a
mandatory question to explain the actual risk involved.
Fixes: b/329611671
Change-Id: Ibfb81d89722c237e4b8a531bcac2d475798369b7
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/357603
Commit-Queue: Jonas Termansen <sortie@google.com>
Reviewed-by: Kevin Chisholm <kevinjchisholm@google.com>
Updates the breaking change template to add the following:
1. Change timeline section: When does the author expect the change to land?
2. Associated CLs: What CLs were necessary to accomplish the change?
Change-Id: If5552600b8760a10599b8606ad584a70e565ad39
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/322374
Reviewed-by: Marya Belanger <mbelanger@google.com>
Reviewed-by: Jonas Termansen <sortie@google.com>
Commit-Queue: Kevin Chisholm <kevinjchisholm@google.com>
- Consolidates "related to" section to what users are familiar with.
- Adds some other related repositories.
- Switches to `dart info` instead of `dart --version` for more information
Change-Id: I70eb03293e5946b51cee7d5a7f02634a593f3bc2
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/320901
Reviewed-by: Devon Carew <devoncarew@google.com>
Commit-Queue: Devon Carew <devoncarew@google.com>
Fixes an indentation error in the breaking change issue for which prevented the issue template from rendering.
Change-Id: I317061671f877e562060b3b75b6fa543efc480c7
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/291041
Reviewed-by: Alexander Thomas <athom@google.com>
Add YAML metadata to the general issue creation template, so
it shows up in the list of issue creation options for users
on the GitHub issue creation page.
Change-Id: I72f546c1dfd407e41ad75e9abcf080cb5c9ea5ec
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/255661
Reviewed-by: Kevin Chisholm <kevinjchisholm@google.com>
Reviewed-by: Michael Thomsen <mit@google.com>
Customers have started using the cherry-pick template to input
feature requests and bug reports. This CL moves the standard issue
template to the top level so it is the first item contributors see when
creating a new issue.
moved original templates
reordered issue templates
Change-Id: I78586c8dc6de673a7ee4d49afe88ce28703b60e4
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/253522
Commit-Queue: Kevin Chisholm <kevinjchisholm@google.com>
Reviewed-by: Kevin Moore <kevmoo@google.com>
Github allows templates to be built in a yaml format.
The current template is built in a query string outside of source control and difficult to update. The updated format provides validation enforcing issue structure and providing ease of creating automations.
Change-Id: Ic9c8b7f13dc67f440cdc827495821ebf162454bd
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/242121
Reviewed-by: Alexander Thomas <athom@google.com>
Commit-Queue: Kevin Chisholm <kevinjchisholm@google.com>
Devon Carew