Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs: Code of Conduct page #16781

Merged
merged 1 commit into from Jan 28, 2023
Merged

docs: Code of Conduct page #16781

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/src/contribute/code-of-conduct.md
View file
Open in desktop
@@ -0,0 +1,10 @@
---
title: Code of Conduct
eleventyNavigation:
key: code of conduct
parent: contribute to eslint
title: Code of Conduct
order: 0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: i realize that it's not standard practice to have this item have order 0. however i would like that we allow this, at least temporarily while doing other IA update PRs as to not create merge conflicts/confusion. if the reviewers' are okay with this approach, i'll create a separate PR for fixing the contribute to eslint navigation order after all the IA updates are done.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The deploy preview confirms that there's no issue with 0 accidentally being treated as falsy, so sure, this makes sense to reduce merge conflicts 👍

---

ESLint welcomes contributions from everyone and adheres to the [OpenJS Foundation Code of Conduct](https://eslint.org/conduct). We kindly request that you read over this code of conduct before contributing.