4.8 KiB
title, intro, redirect_from, versions, type, topics
| title | intro | redirect_from | versions | type | topics | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Scheduling issue creation | You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews. |
|
|
tutorial |
|
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %}
Introduction
This tutorial demonstrates how to use the imjohnbo/issue-bot action to create an issue on a regular basis. For example, you can create an issue each week to use as the agenda for a team meeting.
In the tutorial, you will first make a workflow file that uses the imjohnbo/issue-bot action. Then, you will customize the workflow to suit your needs.
Creating the workflow
-
{% data reusables.actions.choose-repo %}
-
{% data reusables.actions.make-workflow-file %}
-
Copy the following YAML contents into your workflow file.
{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
name: Weekly Team Sync
on:
schedule:
- cron: 20 07 * * 1
jobs:
create_issue:
name: Create team sync issue
runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %}
permissions:
issues: write{% endif %}
steps:
- name: Create team sync issue
uses: imjohnbo/issue-bot@3daae12aa54d38685d7ff8459fc8a2aee8cea98b
with:
assignees: "monalisa, doctocat, hubot"
labels: "weekly sync, docs-team"
title: "Team sync"
body: |
### Agenda
- [ ] Start the recording
- [ ] Check-ins
- [ ] Discussion points
- [ ] Post the recording
### Discussion Points
Add things to discuss below
- [Work this week](https://github.com/orgs/github/projects/3)
pinned: false
close-previous: false
env:
GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
- Customize the parameters in your workflow file:
- Change the value for
on.scheduleto dictate when you want this workflow to run. In the example above, the workflow will run every Monday at 7:20 UTC. For more information about scheduled workflows, see "Scheduled events." - Change the value for
assigneesto the list of {% data variables.product.prodname_dotcom %} usernames that you want to assign to the issue. - Change the value for
labelsto the list of labels that you want to apply to the issue. - Change the value for
titleto the title that you want the issue to have. - Change the value for
bodyto the text that you want in the issue body. The|character allows you to use a multi-line value for this parameter. - If you want to pin this issue in your repository, set
pinnedtotrue. For more information about pinned issues, see "Pinning an issue to your repository." - If you want to close the previous issue generated by this workflow each time a new issue is created, set
close-previoustotrue. The workflow will close the most recent issue that has the labels defined in thelabelsfield. To avoid closing the wrong issue, use a unique label or combination of labels.
- Change the value for
- {% data reusables.actions.commit-workflow %}
Expected results
Based on the schedule parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set pinned to true, the workflow will pin the issue to your repository. If you set close-previous to true, the workflow will close the most recent issue with matching labels.
{% data reusables.actions.schedule-delay %}
You can view the history of your workflow runs to see this workflow run periodically. For more information, see "Viewing workflow run history."
Next steps
- To learn more about additional things you can do with the
imjohnbo/issue-botaction, like rotating assignees or using an issue template, see theimjohnbo/issue-botaction documentation. - Search GitHub for examples of workflows using this action.