Skip to content

Conversation

@cbezault
Copy link
Contributor

No description provided.

@cbezault cbezault added the infrastructure Related to repository automation label May 13, 2020
@cbezault cbezault force-pushed the project-automation branch from 266199a to 9b1ec4d Compare May 13, 2020 15:43
@CaseyCarter
Copy link
Contributor

I find it incredibly amusing that this PR is not associated with the Code Review project =)

@cbezault cbezault force-pushed the project-automation branch 3 times, most recently from 78f5d8e to 9fcbf9b Compare May 13, 2020 16:03
@cbezault cbezault force-pushed the project-automation branch from 9fcbf9b to d1e1cb0 Compare May 13, 2020 16:17
@cbezault
Copy link
Contributor Author

cbezault commented May 13, 2020

It's odd, in my own Repo the action appeared in my PR where here it doesn't. cbezault#7

Edit: Though I guess that's desirable.

@cbezault cbezault changed the title Try out a GH action Use a GitHub action to move new and reopened PRs into the New column May 13, 2020
@cbezault cbezault changed the title Use a GitHub action to move new and reopened PRs into the New column Use a GitHub action to automate PR Review Project May 13, 2020
@cbezault cbezault changed the title Use a GitHub action to automate PR Review Project Use a GitHub Workflow to automate PR Review Project May 13, 2020
@cbezault cbezault changed the title Use a GitHub Workflow to automate PR Review Project Use a GitHub Workflow to automate Code Reviews Project May 13, 2020
@cbezault
Copy link
Contributor Author

Phew, that was a lot of title editing.

@cbezault cbezault marked this pull request as ready for review May 13, 2020 16:29
@cbezault cbezault requested a review from a team as a code owner May 13, 2020 16:29
@CaseyCarter
Copy link
Contributor

Phew, that was a lot of title editing.

Perhaps we need a Github workflow to automate fiddling with the title?

@cbezault
Copy link
Contributor Author

One thing that isn't obvious from this PR is that I added a secret to this repo. I used a PAT associated with my account with the following permissions: public_repo, repo:status, repo_deployment, workflow, write:repo_hook.

I could probably switch it out for one with no hook or deployment permissions if people feel strongly about it.

Copy link
Member

@StephanTLavavej StephanTLavavej 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, thank you! 😸

@cbezault
Copy link
Contributor Author

Okay I changed the token to be public_repo, repo:status, workflow.

@cbezault cbezault merged commit ed2ba34 into microsoft:master May 15, 2020
StephanTLavavej added a commit to StephanTLavavej/STL that referenced this pull request May 18, 2020
Revert "Use a GitHub Workflow to automate Code Reviews Project (microsoft#829)"

This reverts commit ed2ba34.
StephanTLavavej added a commit that referenced this pull request May 19, 2020
Revert "Use a GitHub Workflow to automate Code Reviews Project (#829)"

This reverts commit ed2ba34.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Related to repository automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants