Skip to content
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

workflows: auto-generate maintainer away issue #842

Merged
merged 1 commit into from
Aug 22, 2022

Conversation

ldennington
Copy link
Contributor

@ldennington ldennington commented Aug 17, 2022

Add a new workflow to create issues that will notify GCM users and
contributors of when maintainers are away and the repo is not being
actively monitored. This workflow is controlled by a workflow_dispatch
trigger that requires both a start date and end date for maintainer
absence before running.

@ldennington ldennington self-assigned this Aug 17, 2022
Copy link
Contributor

@derrickstolee derrickstolee left a comment

Choose a reason for hiding this comment

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

Issues could be created using this template by anyone, right? Should we be inviting that kind of activity, or can maintainers create their own issue on the rare occasions that it happens?

@ldennington
Copy link
Contributor Author

ldennington commented Aug 17, 2022

Issues could be created using this template by anyone, right? Should we be inviting that kind of activity, or can maintainers create their own issue on the rare occasions that it happens?

You are correct about this. @mjcheetham and I threw some alternative ideas around in triage this morning. We decided it would be better to automate creation of this type of issue with a workflow that has a workflow dispatch control only maintainers can use. Stay tuned!

@ldennington ldennington changed the title issue templates: add maintainer away notification workflows: auto-generate maintainer away issue Aug 19, 2022
@ldennington
Copy link
Contributor Author

ldennington commented Aug 19, 2022

@derrickstolee @mjcheetham PR has been updated with the new workflow. You can find a sample issue here. In case you're not permitted to view issues in my fork, here's a screenshot as well:

Screen Shot 2022-08-19 at 12 30 48 PM

Any suggestions for improvement are welcome.

.github/workflows/maintainer-absence.yml Outdated Show resolved Hide resolved
Add a new workflow to create issues that will notify GCM users and
contributors of when maintainers are away and the repo is not being
actively monitored. This workflow is controlled by a `workflow_dispatch`
trigger that requires both a start date and end date for maintainer
absence before running.
Copy link
Collaborator

@dscho dscho left a comment

Choose a reason for hiding this comment

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

This is awesome!

@ldennington ldennington merged commit bf690c3 into git-ecosystem:main Aug 22, 2022
@ldennington ldennington mentioned this pull request Nov 3, 2022
ldennington added a commit that referenced this pull request Nov 3, 2022
Changes:

- Check for broken links in documentation (#700)
- Support macOS `arm64` installs via Homebrew (#798) 
- Validate installers before publishing (#813)
- Auto-generate maintainer away notification issues (#842)
- Install dotnet via Jammy feeds on Ubuntu 22.04 and greater (#839)
- Access Azure storage account using service principle credentials
(#851)
- Update documentation to use reference-style links (#680)
- Unify documentation line length (#862)
- Add generic username/password UI (#871)
- Bitbucket DC OAuth support (#607)
- Distribute GCM as a dotnet tool (#886)
- Drop `-core` suffix from entry executable #551 
- Speed up build graph (#924)
@Favourjacobmudiaga

This comment has been minimized.

@ldennington ldennington deleted the ooo-template branch July 12, 2023 18:27
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.

None yet

4 participants