-
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
Conversation
826a929
to
51f082b
Compare
36a43e1
to
34fed93
Compare
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.
Just a few comment. Please review the CodeFactor issues before merging.
- template: [bug.yml, feature.yml] | ||
section: | ||
- id: [frequency] | ||
label: |
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.
|
||
- id: [app-type] | ||
block-list: [] | ||
label: |
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.
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 comment
The 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.
18f315b
to
9e1bd18
Compare
…mote 'synced-files/.github/workflows/Issue-Needs-Attention.yml'
…ed-files/.github/workflows/no-response.yml'
…ed-files/.github/workflows/auto-assign.yml'
…github/auto_assign.yml'
…ced-files/.github/advanced-issue-labeler.yml'
…nced-files/.github/workflows/issue-labeler.yml'
…synced-files/.github/workflows/check-changelog.yml'
…ed-files/.github/ISSUE_TEMPLATE/feature.yml'
9e1bd18
to
d889e29
Compare
Synced local file(s) with realm/ci-actions.
Changed files
LICENSE
with remotesynced-files/LICENSE
.github/workflows/Issue-Needs-Attention.yml
from remotesynced-files/.github/workflows/Issue-Needs-Attention.yml
.github/workflows/no-response.yml
from remotesynced-files/.github/workflows/no-response.yml
.github/workflows/auto-assign.yml
from remotesynced-files/.github/workflows/auto-assign.yml
.github/auto_assign.yml
from remotesynced-files/.github/auto_assign.yml
.github/advanced-issue-labeler.yml
from remotesynced-files/.github/advanced-issue-labeler.yml
.github/workflows/issue-labeler.yml
from remotesynced-files/.github/workflows/issue-labeler.yml
.github/workflows/check-changelog.yml
from remotesynced-files/.github/workflows/check-changelog.yml
.github/ISSUE_TEMPLATE/feature.yml
with remotesynced-files/.github/ISSUE_TEMPLATE/feature.yml
This PR was created automatically by the repo-file-sync-action workflow run #4042772983