From bf855c69b4b0913f8a600d55e2ba3d65459a621d Mon Sep 17 00:00:00 2001 From: Steven Wade Date: Wed, 27 Mar 2024 12:45:53 +0000 Subject: [PATCH] Adding issue template for new Flux org memebership. Signed-off-by: Steven Wade --- .../new-membership-request.yaml | 57 +++++++++++++++++++ .github/workflows/push-website.yaml | 4 +- .github/workflows/update-kubecon.yaml | 4 +- .pre-commit-config.yaml | 14 +++++ PROCESS.md | 2 +- 5 files changed, 76 insertions(+), 5 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/new-membership-request.yaml create mode 100644 .pre-commit-config.yaml diff --git a/.github/ISSUE_TEMPLATE/new-membership-request.yaml b/.github/ISSUE_TEMPLATE/new-membership-request.yaml new file mode 100644 index 00000000..444d46d3 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/new-membership-request.yaml @@ -0,0 +1,57 @@ +--- +name: New membership request +description: Create a membership request to join the FluxCD organization +title: 'REQUEST: New membership for @' +body: + - type: input + validations: + required: true + attributes: + label: GitHub username + description: Your GitHub username + - type: checkboxes + id: membership + attributes: + label: Requirements + description: | + Please confirm that you meet the following requirements: + options: + - label: I have reviewed the community membership guidelines in https://github.com/fluxcd/community/issues/community-roles.md + required: true + - label: I have subscribed to the cncf-flux-dev e-mail list https://lists.cncf.io/g/cncf-flux-dev/join + required: true + - label: I am actively contributing to 1 or more fluxcd GitHub org repos (e.g. Flux, Flagger) + required: true + - label: I have enabled 2FA in GitHub + required: true + - label: I have two sponsors who meet the sponsor requirements listed in the community membership guidelines + required: true + - label: I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application + required: true + - type: textarea + validations: + required: true + attributes: + label: Sponsors + description: | + List the GitHub usernames of the two sponsors who are supporting your membership request. + Sponsors must be existing members of the FluxCD organization. + placeholder: | + @sponsor1 + @sponsor2 + - type: textarea + validations: + required: true + attributes: + label: List of contributions to the Flux project + description: | + Provide a list of contributions you have made to the Flux project. + Contributions can be code, documentation, community support, etc. + - type: checkboxes + id: terms + attributes: + label: Code of Conduct + description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/fluxcd/terraform-provider-flux/blob/main/CODE_OF_CONDUCT.md) + options: + - label: I agree to follow this project's Code of Conduct + required: true diff --git a/.github/workflows/push-website.yaml b/.github/workflows/push-website.yaml index 3bb9b539..44aa2194 100644 --- a/.github/workflows/push-website.yaml +++ b/.github/workflows/push-website.yaml @@ -14,7 +14,7 @@ name: Push to Website # repo, then upon detecting changes fires the "Netlify" workflow in website # to trigger rebuild of https://fluxcd.io (and redeploy of the said content) on: - # + # # workflow-dispatch: # NB: this is disabled on-purpose. The push filter conflicts with workflow-dispatch # # because there is no push event to filter changes based upon. If you want to trigger # # the netlify job in fluxcd/website, go trigger it directly. (You may need access!) @@ -23,7 +23,7 @@ on: # push: branches: - - main + - main jobs: changes: diff --git a/.github/workflows/update-kubecon.yaml b/.github/workflows/update-kubecon.yaml index af05e3e8..5cc4cccb 100644 --- a/.github/workflows/update-kubecon.yaml +++ b/.github/workflows/update-kubecon.yaml @@ -25,9 +25,9 @@ jobs: title: Update from source URL body: | - Detected changes from https://sites.google.com/view/flux-kubecon-paris-2024/home - + Auto-generated by [create-pull-request][1] - + [1]: https://github.com/peter-evans/create-pull-request branch: update-kubecon signoff: true diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml new file mode 100644 index 00000000..f5024e0f --- /dev/null +++ b/.pre-commit-config.yaml @@ -0,0 +1,14 @@ +repos: + - repo: https://github.com/pre-commit/pre-commit-hooks + rev: v4.3.0 + hooks: + - id: check-byte-order-marker + - id: check-case-conflict + - id: check-merge-conflict + - id: check-symlinks + - id: detect-aws-credentials + args: ['--allow-missing-credentials'] + - id: detect-private-key + - id: end-of-file-fixer + - id: mixed-line-ending + - id: trailing-whitespace diff --git a/PROCESS.md b/PROCESS.md index 09c7062e..5fced857 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -104,7 +104,7 @@ Once the above process has taken its course, make sure you - Code changes should go through the pull request process, where the idea and implementation details can be publicly discussed with [Maintainers][Maintainer], other contributors, and end users. Pull requests should only be merged after receiving GitHub approval from at least one Maintainer who is not the pull request author. -- For architectural changes to Flux, please use the [RFC process](https://github.com/fluxcd/flux2/tree/main/rfcs). +- For architectural changes to Flux, please use the [RFC process](https://github.com/fluxcd/flux2/tree/main/rfcs). Note that Flux v2 uses GitHub discussions for (non-architectural) proposals in the `fluxcd/flux2` Git repository . - Non-code changes should be proposed as GitHub issues. If unclear which Git repository to create the issue in, default to the community repository .