diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2023-02-08 20:08:35 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-08 20:08:35 -0800 |
| commit | 7ba72cc836f6f40577bd78c1728c0073a2479ff7 (patch) | |
| tree | 3fc5be4cd180e5b8880788701399145216921672 | |
| parent | 38cccebdcc4bdab5c30c881689bd43ab55a5194a (diff) | |
| parent | 40c4fd254084bff2ef5040eb8b4ec583cddb5b42 (diff) | |
Merge pull request #7129 from cblecker/update-issue
Update issue template for annual reports
| -rw-r--r-- | generator/README.md | 5 | ||||
| -rw-r--r-- | generator/annual-report/github_issue.tmpl | 3 |
2 files changed, 5 insertions, 3 deletions
diff --git a/generator/README.md b/generator/README.md index 787dabd3..6c75e951 100644 --- a/generator/README.md +++ b/generator/README.md @@ -80,9 +80,12 @@ drop GitHub issue templates into the `generator/generated/` directory. You can generate the issues from these templates by running: ```bash -ls -1 generator/generated/*.md | xargs -L1 hub issue create -F +for i in $(ls -1 generator/generated/*.md); do hub issue create -F $i && rm $i; done ``` + You may run into rate limiting issues, which is why this command removes the + files after an issue has been successfully created. + ## Adding custom content diff --git a/generator/annual-report/github_issue.tmpl b/generator/annual-report/github_issue.tmpl index b60870f1..40433612 100644 --- a/generator/annual-report/github_issue.tmpl +++ b/generator/annual-report/github_issue.tmpl @@ -15,8 +15,6 @@ Actions for the chair/organizer of the community group: Once all the above items are complete, this issue may be `/close`'d -A template has already been generated for your group, and is available [here](https://git.k8s.io/community/{{.Dir}}/annual-report-{{lastYear}}.md). - Key dates: - Initial PR to communtiy repo should be opened by March 24th, {{now.UTC.Year}} - PR should be reviewed and merged by April 7th, {{now.UTC.Year}} @@ -31,6 +29,7 @@ If you have any questions or concerns about this process, you may reach the Stee - The public mailing list steering@kubernetes.io - The private mailing list steering-private@kubernetes.io for any private or sensitive issues. +/assign {{range .Leadership.Chairs}}@{{.GitHub}} {{end}} /{{.Prefix}} {{.Label}} /committee steering /area annual-reports |