Alexander Bayandin edccef4514 Make CI more friendly for external contributors (#4663) ...

## Problem

CI doesn't work for external contributors (for PRs from forks), see
#2222 for more information.

I'm proposing the following:
- External PR is created
- PR is reviewed so that it doesn't contain any malicious code
- Label `approved-for-ci-run` is added to that PR (by the reviewer)
- A new workflow picks up this label and creates an internal branch from
that PR (the branch name is `ci-run/pr-*`)
- CI is run on the branch, but the results are also propagated to the
PRs check
- We can merge a PR itself if it's green; if not — repeat.

## Summary of changes
- Create `approved-for-ci-run.yml` workflow which handles
`approved-for-ci-run` label
- Trigger `build_and_test.yml` and `neon_extra_builds.yml` workflows on
`ci-run/pr-*` branches

2023-07-15 11:58:15 +01:00

..

actions

Prevent unintentional Postgres submodule update (#4692)

2023-07-12 15:12:37 +01:00

ISSUE_TEMPLATE

Fix typo in issue template

2022-09-10 01:23:19 +03:00

PULL_REQUEST_TEMPLATE

Add note about manual_release_instructions label (#4015)

2023-04-13 13:13:24 +03:00

workflows

Make CI more friendly for external contributors (#4663)

2023-07-15 11:58:15 +01:00

pull_request_template.md

Simplify github PR template (#4241)

2023-05-16 08:13:54 -04:00