Skip to content

Commit eec21bf

Browse files
erikraserikras
committed
CI
1 parent 4922d9c commit eec21bf

File tree

7 files changed

+291
-0
lines changed

7 files changed

+291
-0
lines changed

‎.github/.github/CODE_OF_CONDUCT.md‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, gender identity and expression, level of
9+
experience, nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or reject
41+
comments, commits, code, wiki edits, issues, and other contributions that are
42+
not aligned to this Code of Conduct, or to ban temporarily or permanently any
43+
contributor for other behaviors that they deem inappropriate, threatening,
44+
offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [email protected]. The project
59+
team will review and investigate all complaints, and will respond in a way that
60+
it deems appropriate to the circumstances. The project team is obligated to
61+
maintain confidentiality with regard to the reporter of an incident. Further
62+
details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
71+
version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
72+
73+
[homepage]: http://contributor-covenant.org
74+
[version]: http://contributor-covenant.org/version/1/4/

‎.github/.github/CONTRIBUTING.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
# Contributing
2+
3+
Thanks for your interest in contributing to 🏁 Final Form! Please take a moment
4+
to review this document **before submitting a pull request**.
5+
6+
We are open to, and grateful for, any contributions made by the community.
7+
8+
## Reporting issues and asking questions
9+
10+
Before opening an issue, please search the
11+
[issue tracker](https://github.com/final-form/final-form/issues) to make sure
12+
your issue hasn’t already been reported.
13+
14+
**We use the issue tracker to keep track of bugs and improvements** to 🏁 Final
15+
Form itself, its examples, and the documentation. We encourage you to open
16+
issues to discuss improvements, architecture, internal implementation, etc. If a
17+
topic has been discussed before, we will ask you to join the previous
18+
discussion.
19+
20+
For support or usage questions, please search and ask on
21+
[StackOverflow with a `final-form` tag](https://stackoverflow.com/questions/tagged/final-form).
22+
We ask you to do this because StackOverflow has a much better job at keeping
23+
popular questions visible. Unfortunately good answers get lost and outdated on
24+
GitHub.
25+
26+
**If you already asked at StackOverflow and still got no answers, post an issue
27+
with the question link, so we can either answer it or evolve into a bug/feature
28+
request.**
29+
30+
## Sending a pull request
31+
32+
**Please ask first before starting work on any significant new features.**
33+
34+
It's never a fun experience to have your pull request declined after investing a
35+
lot of time and effort into a new feature. To avoid this from happening, we
36+
request that contributors create
37+
[an issue](https://github.com/final-form/final-form/issues) to first discuss any
38+
significant new features.
39+
40+
Please try to keep your pull request focused in scope and avoid including
41+
unrelated commits.
42+
43+
After you have submitted your pull request, we’ll try to get back to you as soon
44+
as possible. We may suggest some changes or improvements.
45+
46+
Please format the code before submitting your pull request by running:
47+
48+
```sh
49+
npm run precommit
50+
```
51+
52+
## Coding standards
53+
54+
Our code formatting rules are defined in
55+
[.eslintrc](https://github.com/final-form/final-form/blob/main/.eslintrc). You
56+
can check your code against these standards by running:
57+
58+
```sh
59+
npm start lint
60+
```
61+
62+
To automatically fix any style violations in your code, you can run:
63+
64+
```sh
65+
npm run precommit
66+
```
67+
68+
## Running tests
69+
70+
You can run the test suite using the following commands:
71+
72+
```sh
73+
npm test
74+
```
75+
76+
Please ensure that the tests are passing when submitting a pull request. If
77+
you're adding new features to 🏁 Final Form, please include tests.

‎.github/.github/FUNDING.yml‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# These are supported funding model platforms
2+
3+
github: erikras
4+
patreon: erikras
5+
open_collective: final-form
6+
ko_fi: # Replace with a single Ko-fi username
7+
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8+
community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9+
liberapay: # Replace with a single Liberapay username
10+
issuehunt: # Replace with a single IssueHunt username
11+
otechie: # Replace with a single Otechie username
12+
custom: # Replace with a single custom sponsorship URL

‎.github/.github/ISSUE_TEMPLATE.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
<!--
2+
3+
👋 Hey, thanks for taking an interest in 🏁 Final Form!
4+
5+
-->
6+
7+
### Are you submitting a **bug report** or a **feature request**?
8+
9+
<!-- For support request, please use Stack Overflow instead. This issue tracker is reserved for bugs and features. -->
10+
11+
### What is the current behavior?
12+
13+
<!-- If this is a bug, please include steps to reproduce and a minimal demo of the problem using Sandbox, Plunkr, WebpackBin or JSFiddle. -->
14+
15+
### What is the expected behavior?
16+
17+
### Sandbox Link
18+
19+
<!-- Problems are much easier to understand and debug if they can be demonstrated in a minimal environment. -->
20+
21+
### What's your environment?
22+
23+
<!-- Include 🏁 Final Form version, OS/browser affected, Node version, etc. -->
24+
25+
### Other information
26+
27+
<!-- Include here any detailed explanation, stacktraces, related issues, links for Stack Overflow, Twitter, etc. -->

‎.github/.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
<!--
2+
3+
👋 Hey, thanks for your interest in contributing to 🏁 Final Form Arrays!
4+
5+
**Please ask first before starting work on any significant new features.**
6+
7+
It's never a fun experience to have your pull request declined after investing a
8+
lot of time and effort into a new feature. To avoid this from happening, we
9+
request that contributors create an issue to first discuss any significant new
10+
features.
11+
12+
Please try to keep your pull request focused in scope and avoid including
13+
unrelated commits.
14+
15+
After you have submitted your pull request, we’ll try to get back to you as soon
16+
as possible. We may suggest some changes or improvements.
17+
18+
Please format the code before submitting your pull request by running:
19+
20+
```
21+
npm run precommit
22+
```
23+
24+
https://github.com/final-form/final-form-arrays/blob/main/.github/CONTRIBUTING.md
25+
26+
-->

‎.github/.github/workflows/ci.yml‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
name: CI
2+
3+
on: [push]
4+
5+
jobs:
6+
lint:
7+
name: Lint
8+
runs-on: ubuntu-latest
9+
10+
steps:
11+
- uses: actions/checkout@v2
12+
- name: Use Node.js ${{ matrix.node_version }}
13+
uses: actions/setup-node@v2
14+
with:
15+
node-version: "22"
16+
- name: Prepare env
17+
run: yarn install --ignore-scripts --frozen-lockfile
18+
- name: Run linter
19+
run: yarn start lint
20+
21+
prettier:
22+
name: Prettier Check
23+
runs-on: ubuntu-latest
24+
25+
steps:
26+
- uses: actions/checkout@v2
27+
- name: Use Node.js ${{ matrix.node_version }}
28+
uses: actions/setup-node@v2
29+
with:
30+
node-version: "22"
31+
- name: Prepare env
32+
run: yarn install --ignore-scripts --frozen-lockfile
33+
- name: Run prettier
34+
run: yarn start prettier
35+
36+
test:
37+
name: Unit Tests
38+
runs-on: ubuntu-latest
39+
40+
steps:
41+
- uses: actions/checkout@v2
42+
- name: Use Node.js ${{ matrix.node_version }}
43+
uses: actions/setup-node@v2
44+
with:
45+
node-version: "22"
46+
- name: Prepare env
47+
run: yarn install --ignore-scripts --frozen-lockfile
48+
- name: Run unit tests
49+
run: yarn start test
50+
- name: Run code coverage
51+
uses: codecov/[email protected]

‎.github/.github/workflows/lock.yml‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
name: "Lock Threads"
2+
3+
on:
4+
schedule:
5+
- cron: "0 * * * *"
6+
workflow_dispatch:
7+
8+
permissions:
9+
issues: write
10+
pull-requests: write
11+
12+
concurrency:
13+
group: lock
14+
15+
jobs:
16+
action:
17+
runs-on: ubuntu-latest
18+
steps:
19+
- uses: dessant/lock-threads@v3
20+
with:
21+
issue-inactive-days: "365"
22+
issue-lock-reason: "resolved"
23+
pr-inactive-days: "365"
24+
pr-lock-reason: "resolved"

0 commit comments

Comments
 (0)