exivity / actions Goto Github PK

See e.g. https://github.com/exivity/actions/runs/5335739848?check_suite_focus=true

docker: Error response from daemon: hcsshim::CreateComputeSystem 68f8b518cc34278435aed1ae775cd58db5812d45da14b06c49c0abaea0462a41: The container operating system does not match the host operating system.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Include an option to exclude or only include certain file (patterns) for accepting PR's.

When the exclude option is set and only files are modified that match the exclude option, auto-approve (set status and add review approval) PR.

If the include option is set and no files are modified that match the include option, auto-approve (set status and add review approval) PR.

In all other cases, proceed with the 'normal' scaffold accept process.

This issue provides visibility into Renovate updates and their statuses. Learn more

This repository currently has no open or pending branches.

• Check this box to trigger a request for Renovate to run again on this repository

See e.g. https://github.com/exivity/proximity/runs/3045594784?check_suite_focus=true

Mimick https://github.com/probot/settings, implement as an action
Convert to action, draw inspiration from https://github.com/elstudio/actions-settings

Also add option to sync:

• default workflows (as pr)
• default codeowners contents (as pr)

Sending large files to VirusTotal fails (limit seems to be around 150 MB). To fix this, https://developers.virustotal.com/reference/files-upload-url can be used in the virustotal action.

Relates to EXVT-5111

Rationale
Sometimes we know that a change will not affect the acceptance tests (e.g. adding dependabot.yml config). It would be nice to be able to skip the tests in this case by adding a certain label to the PR.

Proposal
When the label no-accept-needed is added, approve PR in accept action and write commit status. If possible, remove when unlabeled.

Implementation

• Implement logic in accept action
• Add pull_request.labeled (and pull_request.unlabeled?) events to accept workflow examples
• Update .github repo settings file with label

Hi there! I came across your repo via repository-settings/app#518 (comment)

I feel like your solution here is really great, but it seems that I can't actually use this GitHub Action outside the context of exivity. Is that correct?

These are my failed attempts, for what it's worth:
https://github.com/g0v-network/domains/actions/workflows/sync-repo-settings.yml

Curious to know your thoughts! Wondering if maybe (so as not to get in the way of your monorepo flow) the org owner could just be made more configurable here, as I believe that's part of the snag :)

PS, you might get a kick out of using this github action to get ephemeral tokens from a github app scoped to just your organization: https://github.com/peter-murray/workflow-application-token-action