You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore(biomejs): improve config and enable for vscode
* chore(vscode): add organizeImports action to code actions on save
* chore: add std-env dependency, update types, and improve request handling
* chore: refine request parameters handling and cleanup undefined values
* chore: add actions and emotes sheets to XIVAPI and update tests for achievements
* chore: rename verify-publish job to publish in CI workflow
* chore: update README for clarity, improve usage examples, and enhance documentation
* chore: improve example section formatting in README
* chore: add output example for search sheets in README
* chore: add Code of Conduct and contributing guidelines to improve community standards and documentation
Our goal is to foster a respectful, welcoming, and collaborative space across every project in this monorepo. Everyone involved shares the responsibility of keeping participation positive and free from harassment.
4
+
5
+
## Our Standards
6
+
7
+
We encourage behaviors that help build a healthy and productive community:
8
+
9
+
- Using welcoming and inclusive language
10
+
- Respecting differing viewpoints and experiences
11
+
- Offering and receiving constructive feedback gracefully
12
+
- Showing empathy and kindness toward others
13
+
- Collaborating in ways that support the long‑term health of the project
14
+
15
+
## Unacceptable Behavior
16
+
17
+
The following behaviors are not acceptable in any project within this monorepo:
18
+
19
+
- Harassment, discrimination, or exclusion based on personal characteristics
20
+
- Personal attacks, insults, or trolling
21
+
- Public or private harassment of any kind
22
+
- Deliberate intimidation or threats
23
+
- Disruptive behavior that interferes with constructive collaboration
24
+
25
+
## Enforcement
26
+
27
+
If you observe or experience behavior that violates this Code of Conduct, please contact the maintainers through the repository’s issue tracker or by opening a private security advisory.
28
+
29
+
All reports will be handled confidentially.
30
+
Maintainers are responsible for reviewing incidents, determining appropriate actions, and enforcing this Code of Conduct fairly and consistently across the monorepo.
31
+
32
+
## Attribution
33
+
34
+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/) version 2.1.
Thanks for your interest in contributing! We welcome contributions of all kinds, including bug fixes, new features, documentation improvements, and — eventually — translations.
4
+
5
+
## How to Contribute
6
+
7
+
1. **Fork** the repository.
8
+
2. **Create a feature branch**, for example:
9
+
```bash
10
+
git checkout -b feature/your-feature-name
11
+
```
12
+
3. Make your changes, following the style and structure of the project or package you are modifying.
13
+
4. Add tests or verify that your changes work as expected.
14
+
5. Commit your work using clear, descriptive commit messages.
15
+
6. Push your branch:
16
+
```bash
17
+
git push origin feature/your-feature-name
18
+
```
19
+
7. Open a Pull Request.
20
+
In your PR description, include:
21
+
22
+
- What you changed
23
+
- Why you changed it
24
+
- Any related issues or context
25
+
26
+
## Reporting Issues
27
+
28
+
Before opening a new issue:
29
+
30
+
- Check existing issues to avoid duplicates.
31
+
- Provide a clear description of the problem or feature request.
32
+
- For bugs, include steps to reproduce, expected vs. actual behavior, and any relevant logs or screenshots.
33
+
- For feature requests, explain the problem the feature solves and any alternatives you’ve considered.
34
+
35
+
## Code Style & Tests
36
+
37
+
- Follow the existing coding conventions (formatting, naming, structure).
38
+
- Update or add tests when appropriate.
39
+
- Ensure all tests pass before submitting your PR (if a test suite is available).
40
+
- Keep changes focused—smaller, well‑scoped PRs are easier to review and merge.
41
+
42
+
## Community Code of Conduct
43
+
44
+
By contributing to this monorepo, you agree to follow our [Code of Conduct](./CODE_OF_CONDUCT.md).
@@ -96,17 +91,8 @@ console.log(versions[0]); // e.g. "7.0"
96
91
97
92
## Contributing
98
93
99
-
We welcome all contributions! Whether you'd like to report a bug, suggest a feature, improve the documentation, or submit a pull request, your help is appreciated.
100
-
101
-
To get started, clone the repository with: `git clone https://github.com/xivapi/xivapi-js.git`
102
-
103
-
Before opening a pull request, please:
104
-
105
-
- Make sure your code passes linting and all current tests (`npm run lint && npm test`).
106
-
- Clearly explain your changes and reference any relevant issues in your PR description.
107
-
108
-
If you have questions, suggestions, or want to discuss changes before contributing, feel free to open an issue!
94
+
Contributions, bug reports, and feature requests are welcome! See [`CONTRIBUTING`](CONTRIBUTING) for guidelines on how to get started.
109
95
110
96
## License
111
97
112
-
MIT License - see [LICENSE](LICENSE) file for details.
98
+
This project is licensed under the MIT License. See [`LICENSE`](LICENSE) for details.
0 commit comments