feat: add support to archive repositories #226
Conversation
|
Not sure why both jobs are failing. 🤔 |
@dirien it's because you want to merge a branch from a fork. The repo is still not configured in a way that secrets are passed to workflow runs that started from a fork. This is an outstanding issue that @ringods and I worked upon but never came to a satisfiable solution. |
|
@tmeckel: I have no permission to create a branch in this repo. |
|
@dirien no need to close the PR. I'll review and merge when I've time. Sorry if my initial answer was misunderstandable in that way. |
|
@tmeckel sounds good! Thanks! |
There was a problem hiding this comment.
@dirien I would set hasIssues to false, if a repository is archived hasIssues: args.archived === true ? false : true. Because it makes no sense to enable issues on an archived repository.
Same with vulnerabilityAlerts: vulnerabilityAlerts: args.archived === true ? false : true,
|
@tmeckel done |
|
Approved, after running
|
This PR add support to archive a provider.
👀 @ringods @tmeckel