-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Agenda_Issue.yml #112
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
name: Weekly Team Sync | ||
on: | ||
schedule: | ||
- cron: 00 7 * * 1 | ||
|
||
jobs: | ||
create_issue: | ||
name: Create team sync issue | ||
runs-on: ubuntu-latest | ||
permissions: | ||
issues: write | ||
steps: | ||
- name: Create team sync issue | ||
uses: imjohnbo/issue-bot@3daae12aa54d38685d7ff8459fc8a2aee8cea98b | ||
with: | ||
assignees: "" | ||
labels: "community, meeting" | ||
title: "Community Meeting !" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the date inside the title is relevant, must be included in my opinion. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How can we add the dynamic date to title? |
||
body: | | ||
### Agenda | ||
|
||
- [ ] Check-ins | ||
- [ ] Discussion points | ||
- Please add a topic in this thread and add a link to the GitHub issue associated with the topic. | ||
- Please make sure you give folks enough time to review/discuss the topic offline on GitHub before coming into the meeting | ||
- (optional) Paste the image of an animal smile_cat | ||
|
||
### Discussion Points | ||
Add things to discuss below | ||
|
||
pinned: true | ||
AmanSarraf marked this conversation as resolved.
Show resolved
Hide resolved
|
||
close-previous: true | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this is not desired, sometimes we want to keep the previous issues open until someone puts there a summary or similar of the community call. |
||
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
per the issue, this needs to run after the community meeting on Monday. I think here is UTC, so it should be something like 00 17 * * 1