-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🔄 Synced file(s) with realm/ci-actions #8091
Changes from all commits
92a6313
d617650
f705111
25fbe04
581f9ac
791d3e5
4434fe2
1993c6e
d889e29
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
# NOTE: This is a common file that is overwritten by realm/ci-actions sync service | ||
# and should only be modified in that repository. | ||
|
||
# syntax - https://github.com/redhat-plumbers-in-action/advanced-issue-labeler#policy | ||
# Below keys map from the option used in issue form dropdowns to issue labels | ||
# Limitation: | ||
# Currently it's not possible to use strings containing ,␣ in the dropdown menus in the issue forms. | ||
|
||
--- | ||
|
||
policy: | ||
- template: [bug.yml, feature.yml] | ||
section: | ||
- id: [frequency] | ||
label: | ||
- name: 'Frequency:Once' | ||
keys: ['Once'] | ||
- name: 'Frequency:Sometimes' | ||
keys: ['Sometimes'] | ||
- name: 'Frequency:Always' | ||
keys: ['Always'] | ||
|
||
- id: [repro] | ||
label: | ||
- name: 'Repro:Always' | ||
keys: ['Always'] | ||
- name: 'Repro:Sometimes' | ||
keys: ['Sometimes'] | ||
- name: 'Repro:No' | ||
keys: ['No'] | ||
|
||
- id: [sync, flavour, services] | ||
block-list: [] | ||
label: | ||
- name: 'SDK-Use:Local' | ||
keys: ['Local Database only'] | ||
- name: 'SDK-Use:Sync' | ||
keys: ['Atlas Device Sync'] | ||
- name: 'SDK-Use:Services' | ||
keys: ['Atlas App Services: Function or GraphQL or DataAPI etc'] | ||
- name: ['SDK-Use:All'] | ||
keys: ['Both Atlas Device Sync and Atlas App Services'] | ||
|
||
- id: [encryption] | ||
block-list: [] | ||
label: | ||
- name: 'Encryption:On' | ||
keys: ['Yes'] | ||
- name: 'Encryption:Off' | ||
keys: ['No'] | ||
|
||
- id: [app-type] | ||
block-list: [] | ||
label: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. in a RealmSwift context, most of the app don't enter in any of this types. Is this relevant to other SDKs and that's why it is here? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes, this is only relevant for .NET. But we use the same common config file. It will have no effect for Swift. |
||
- name: 'App-type:Unity' | ||
keys: ['Unity'] | ||
- name: 'App-type:Xamarin' | ||
keys: ['Xamarin'] | ||
- name: 'App-type:WPF' | ||
keys: ['WPF'] | ||
- name: 'App-type:Console' | ||
keys: ['Console or Server'] | ||
- name: 'App-type:Other' | ||
keys: ['Other'] | ||
|
||
- id: [importance] | ||
block-list: [] | ||
label: | ||
- name: 'Importance:Dealbraker' | ||
keys: ['Dealbreaker'] | ||
- name: 'Importance:Major' | ||
keys: ['Would be a major improvement'] | ||
- name: 'Importance:Workaround' | ||
keys: ['I would like to have it but have a workaround'] | ||
- name: 'Importance:Nice' | ||
keys: ['Fairly niche but nice to have anyway'] |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
addAssignees: author | ||
addReviewers: false | ||
runOnDraft: true |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# NOTE: This is a common file that is overwritten by realm/ci-actions sync service | ||
# and should only be modified in that repository. | ||
|
||
name: Issue Needs Attention | ||
# This workflow is triggered on issue comments. | ||
on: | ||
issue_comment: | ||
types: created | ||
|
||
jobs: | ||
applyNeedsAttentionLabel: | ||
uses: realm/ci-actions/.github/workflows/issue-needs-attention.yml@main |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# NOTE: This is a common file that is overwritten by realm/ci-actions sync service | ||
# and should only be modified in that repository. | ||
|
||
name: 'Auto Assign' | ||
on: | ||
pull_request: | ||
types: [opened] | ||
|
||
jobs: | ||
add-assignee: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: kentaro-m/auto-assign-action@248761c4feb3917c1b0444e33fad1a50093b9847 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# NOTE: This is a common file that is overwritten by realm/ci-actions sync service | ||
# and should only be modified in that repository. | ||
|
||
name: "Check Changelog" | ||
on: | ||
pull_request: | ||
types: [opened, synchronize, reopened, ready_for_review, labeled, unlabeled] | ||
|
||
jobs: | ||
changelog: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@8230315d06ad95c617244d2f265d237a1682d445 | ||
with: | ||
submodules: false | ||
- name: Enforce Changelog | ||
uses: dangoslen/changelog-enforcer@c0b9fd225180a405c5f21f7a74b99e2eccc3e951 | ||
with: | ||
skipLabels: no-changelog | ||
missingUpdateErrorMessage: Please add an entry in CHANGELOG.md or apply the 'no-changelog' label to skip this check. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# NOTE: This is a common file that is overwritten by realm/ci-actions sync service | ||
# and should only be modified in that repository. | ||
|
||
# See configuration in .github/advanced-issue-labeler.yml | ||
|
||
name: Issue labeler (policy) | ||
on: | ||
issues: | ||
types: [ opened ] | ||
|
||
jobs: | ||
label-issues-policy: | ||
runs-on: ubuntu-latest | ||
permissions: | ||
issues: write | ||
|
||
strategy: | ||
matrix: | ||
template: [ bug.yml, feature.yml ] | ||
|
||
steps: | ||
- uses: actions/checkout@v3 | ||
|
||
- name: Parse issue form | ||
uses: stefanbuck/github-issue-parser@c1a559d78bfb8dd05216dab9ffd2b91082ff5324 # v3.0.1 | ||
id: issue-parser | ||
with: | ||
template-path: .github/ISSUE_TEMPLATE/${{ matrix.template }} | ||
|
||
- name: Set labels based on policy | ||
uses: redhat-plumbers-in-action/advanced-issue-labeler@6ee6fddfd744ee26b977e6a0436916f256896971 # v2.0.3 | ||
with: | ||
issue-form: ${{ steps.issue-parser.outputs.jsonString }} | ||
template: ${{ matrix.template }} | ||
token: ${{ secrets.GITHUB_TOKEN }} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# NOTE: This is a common file that is overwritten by realm/ci-actions sync service | ||
# and should only be modified in that repository. | ||
|
||
name: No Response | ||
|
||
# Both `issue_comment` and `scheduled` event types are required for this Action | ||
# to work properly. | ||
on: | ||
issue_comment: | ||
types: [created] | ||
schedule: | ||
# Schedule at 00:00 every day | ||
- cron: '0 0 * * *' | ||
|
||
jobs: | ||
noResponse: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: lee-dohm/[email protected] | ||
with: | ||
token: ${{ github.token }} | ||
responseRequiredLabel: More-information-needed |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -174,4 +174,4 @@ | |
of your accepting any such warranty or additional liability. | ||
|
||
END OF TERMS AND CONDITIONS | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we also want to know how many users is affecting?, (all, many, just a few or once). I think is a different information than frequency and also can help us prioritise the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah if we think that would be useful. Perhaps we can add that as a separate PR?
When i'm thinking about "reach", I'm mostly thinking about if it affect many apps versus many users of a single app. But it's surely relevant.