Skip to content

CODE_OF_CONDUCT #302

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

Merged
merged 3 commits into from
Aug 26, 2020
Merged

CODE_OF_CONDUCT #302

merged 3 commits into from
Aug 26, 2020

Conversation

Gaushikmr
Copy link
Contributor

No description provided.

@Gaushikmr Gaushikmr requested a review from benlangmuir as a code owner August 9, 2020 06:07
@benlangmuir
Copy link
Contributor

sourcekit-lsp is under the same code of conduct as the rest of the Swift project: https://swift.org/community/#code-of-conduct. Rather than maintain a separate copy of the CoC in this repository, could we link to the one on Swift.org instead?

# Code of Conduct

The code of conduct for this project can be found at https://swift.org/community/#code-of-conduct

@Gaushikmr
Copy link
Contributor Author

@benlangmuir OK

@benlangmuir
Copy link
Contributor

I was suggesting we link to it rather than copy - see my suggested wording in my previous comment.

@Gaushikmr
Copy link
Contributor Author

@benlangmuir just to link

@Gaushikmr
Copy link
Contributor Author

Gaushikmr commented Aug 25, 2020

@benlangmuir
Copy link
Contributor

Hi @Gaushikmr, perhaps there was some confusion here. I was asking that we change the contents of CODE_OF_CONDUCT.md to

# Code of Conduct

The code of conduct for this project can be found at https://swift.org/community/#code-of-conduct

@benlangmuir
Copy link
Contributor

@swift-ci please test

1 similar comment
@benlangmuir
Copy link
Contributor

@swift-ci please test

@benlangmuir benlangmuir merged commit 5ac9e60 into swiftlang:master Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants