Skip to content

Conversation

AmanSarraf
Copy link

Created a workflow yml to automate the Agenda issue creation,
Fixes #79

@openshift-ci openshift-ci bot requested review from adambkaplan and otaviof October 26, 2022 05:06
@openshift-ci
Copy link

openshift-ci bot commented Oct 26, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sbose78 for approval by writing /assign @sbose78 in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

@qu1queee qu1queee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AmanSarraf many thanks! I left some comments on the action setup. Please take a look.

with:
assignees: ""
labels: "community, meeting"
title: "Community Meeting !"
Copy link
Contributor

Choose a reason for hiding this comment

The 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.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How can we add the dynamic date to title?

name: Weekly Team Sync
on:
schedule:
- cron: 00 7 * * 1
Copy link
Contributor

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

Add things to discuss below

pinned: true
close-previous: true
Copy link
Contributor

Choose a reason for hiding this comment

The 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.

@AmanSarraf AmanSarraf closed this by deleting the head repository Dec 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add GitHub action that automatically opens issue for community meeting

2 participants