Commit Graph

6 Commits

Author SHA1 Message Date
Javi Martín
629756dd15 Change URLs referencing our GitHub repositories 2023-07-12 16:05:26 +02:00
Alex
bb52adec37 Update kanban.yml
repository-projects: write is not needed because secrets.KANBAN_TOKEN is used
2022-09-20 19:39:46 +01:00
Alex
40886704bb Update kanban.yml
Signed-off-by: sashashura <93376818+sashashura@users.noreply.github.com>
2022-08-29 20:07:04 +01:00
Javi Martín
b86c4ec100 Use a better name for the kanban workflow
The word "assign" was ambiguous, because it could have meant we were
assigning the author.

We were also displaying the same name twice.
2022-07-07 14:28:02 +02:00
Javi Martín
187e6ee1d6 Don't run kanban assignment on forks
Without this condition, the kanban assignment would be run on every
CONSUL fork and that would result in unpredictable results since they
would try to write on our kanban, and they don't have permission to do
so.

Note that, much to my dismay :D, the code only works if we use single
quotes in the name of the repository owner; it doesn't work if we use
double quotes.
2022-07-06 16:33:54 +02:00
Javi Martín
7015f41e3a Add kanban automation for new pull requests
So now, newly opened pull requests will automatically be added to the
"Reviewing" column, while newly opened draft pull requests will
automatically be added to the "Doing" column.

I've added the "reopened" event just in case (and was indeed very useful
while testing this feature), although we rarely reopen pull requests.

Note that this only works on pull requests that aren't already in the
project; that is, if a pull request is already in the "Doing" column,
closing it and reopening it will *not* move it to the "Reviewing
column".

So it looks like we won't easily be able to extend this feature in order
to automatically move pull requests when they're marked as ready for
review.
2022-06-08 15:49:03 +02:00