Skip to content

Comments

chore: adding workflow to add issues to docs on docs needed label#1178

Merged
TomAFrench merged 8 commits intomasterfrom
zepedro/migrating-issues
Apr 24, 2023
Merged

chore: adding workflow to add issues to docs on docs needed label#1178
TomAFrench merged 8 commits intomasterfrom
zepedro/migrating-issues

Conversation

@signorecello
Copy link
Contributor

@signorecello signorecello commented Apr 19, 2023

Description

Summary of changes

It creates a new workflow that automatically creates new issues in the docs repo when someone assigns the "doc needed" label here

Checklist

  • I have tested the changes locally.
  • I have formatted the changes with Prettier and/or cargo fmt with default settings.
  • I have linked this PR to the issue(s) that it resolves.
  • I have reviewed the changes on GitHub, line by line.
  • I have ensured all changes are covered in the description.

@TomAFrench
Copy link
Member

Can you trim out the generic comments from the workflows? They're adding noise to the files.

We could also merge these two workflows into one.

@signorecello
Copy link
Contributor Author

done @TomAFrench

Copy link
Member

@TomAFrench TomAFrench left a comment

Choose a reason for hiding this comment

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

We don't need two copies of the dispatch_open and dispatch_close job afaict. We only need to change the workflow id between them so we should just need an "if-else" on that argument.

@signorecello
Copy link
Contributor Author

thanks @TomAFrench just did that 👍

Co-authored-by: Blaine Bublitz <blaine.bublitz@gmail.com>
@TomAFrench TomAFrench self-requested a review April 19, 2023 18:41
@kevaundray kevaundray enabled auto-merge April 20, 2023 18:53
@kevaundray
Copy link
Contributor

Leaving this to @phated as I don't know enough about the CI

Co-authored-by: Blaine Bublitz <blaine.bublitz@gmail.com>
phated
phated previously approved these changes Apr 20, 2023
Copy link
Contributor

@phated phated left a comment

Choose a reason for hiding this comment

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

LGTM!

@signorecello
Copy link
Contributor Author

@TomAFrench can you review this so it gets merged?

TomAFrench
TomAFrench previously approved these changes Apr 21, 2023
@kevaundray kevaundray added this pull request to the merge queue Apr 21, 2023
@TomAFrench TomAFrench removed this pull request from the merge queue due to a manual request Apr 21, 2023
@TomAFrench
Copy link
Member

Actually, @signorecello could we merge the workflows that this workflow will be triggering first before we merge this? Not sure how GH will react to a missing workflow.

@TomAFrench TomAFrench added this pull request to the merge queue Apr 21, 2023
@TomAFrench TomAFrench removed this pull request from the merge queue due to a manual request Apr 21, 2023
@TomAFrench TomAFrench added this pull request to the merge queue Apr 21, 2023
@TomAFrench TomAFrench removed this pull request from the merge queue due to a manual request Apr 21, 2023
@TomAFrench
Copy link
Member

Holding off for a little bit due to #1193 (comment)

@TomAFrench TomAFrench enabled auto-merge April 21, 2023 20:22
@signorecello signorecello dismissed stale reviews from TomAFrench and phated via 5087abb April 24, 2023 14:45
@TomAFrench TomAFrench added this pull request to the merge queue Apr 24, 2023
Merged via the queue into master with commit 48995b4 Apr 24, 2023
@TomAFrench TomAFrench deleted the zepedro/migrating-issues branch April 24, 2023 18:46
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.

4 participants