From bf1acb4e8dd5fa16682147f282746d508631b0f2 Mon Sep 17 00:00:00 2001 From: Daniel Schmidt Date: Tue, 7 Jan 2025 12:35:53 +0100 Subject: [PATCH] fix typo Co-authored-by: Liam Cervante --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index ac800c506d9c..e8f99a0f9b15 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -122,7 +122,7 @@ If an an unmaintained area of code interests you and you'd like to become a main 1. You are welcome to submit a [draft pull request](https://github.blog/2019-02-14-introducing-draft-pull-requests/) for commentary or review before it is fully completed. It's also a good idea to include specific questions or items you'd like feedback on. 2. Once you believe your pull request is ready to be merged you can create your pull request. 3. If your change is user-facing, add a short description in a changelog entry. -You can use `npx changie new` to create a new changelog entry or manually create a new file in the .changes/unreleasd directory. +You can use `npx changie new` to create a new changelog entry or manually create a new file in the .changes/unreleased directory. 4. When time permits Terraform's core team members will look over your contribution and either merge, or provide comments letting you know if there is anything left to do. It may take some time for us to respond. We may also have questions that we need answered about the code, either because something doesn't make sense to us or because we want to understand your thought process. We kindly ask that you do not target specific team members. 5. If we have requested changes, you can either make those changes or, if you disagree with the suggested changes, we can have a conversation about our reasoning and agree on a path forward. This may be a multi-step process. Our view is that pull requests are a chance to collaborate, and we welcome conversations about how to do things better. It is the contributor's responsibility to address any changes requested. While reviewers are happy to give guidance, it is unsustainable for us to perform the coding work necessary to get a PR into a mergeable state. 6. Once all outstanding comments and checklist items have been addressed, your contribution will be merged! Merged PRs may or may not be included in the next release based on changes the Terraform teams deems as breaking or not. The core team takes care of updating the [CHANGELOG.md](https://github.com/hashicorp/terraform/blob/main/CHANGELOG.md) as they merge.