# Pull Request
## 📖 Description
This change replaces `yarn` and `lerna` with `npm` workspaces. This should help a lot with dependency management as we were on yarn 1 which had a fairly heavily manipulated dependency tree.
The changes also upgrade most dependencies to their latest versions and the changes may reflect this, such as updating all versions of webpack to webpack 5.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://github.com/microsoft/fast/blob/master/CODE_OF_CONDUCT.md#our-standards) for this project.
# Pull Request
## 📖 Description
This change removes:
- `@microsoft/fast-foundation` - the most recent version can be found on branch `archives/fast-foundation-3`
- `@microsoft/fast-web-utilities`
### 🎫 Issues
Closes#6951 and closes#6954
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://github.com/microsoft/fast/blob/master/CODE_OF_CONDUCT.md#our-standards) for this project.
## ⏭ Next Steps
- File an issue to remove dependency on `@microsoft/fast-foundation` in `@microsoft/fast-ssr` for testing.
# Pull Request
## 📖 Description
This update to the docs:
- Re-aligns docs around `@microsoft/fast-element`
- Adds more docs around the `html`, `css` and `FASTElement` exports
## 👩💻 Reviewer Notes
There are 3 `TODO` marked documents that require separate PRs and reviews:
- DI (Dependency Injection)
- Migration (from `@microsoft/fast-element` v1 to v2) there may not be any breaking changes but there might be some suggestions for users looking to update their package
- Component library - with #6955 we are looking to assist the community in the creation of packages built on the `@microsoft/fast-element` package, this should provide some best practices and guidance on doing this.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://github.com/microsoft/fast/blob/master/CODE_OF_CONDUCT.md#our-standards) for this project.
## ⏭ Next Steps
- Fill in the `TODO` docs in separate PRs
* remove fast-components package
* remove component explorer
* Change files
* remove references on the readme
* remove playwright from validate workflow which was only used in components
* fix test typings that were throwing
* Change files
* remove component explore workflow
* update to fix bad links, grammar, and add dictionary items to vscode workspaces
* update to remove fixme tag because the item has already been closed and work completed
* Change files
* upgrade to latest beta
* update for consistent formatting
* update patch to type none
* update link
* update grammar based on review feedback
* update grammar
* update to remove duplicates
* remove controversial updates
* update to replace absolute path with relative paths to ensure works across both production and staging environments
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This pull request adds documentation to the contribution policy which updates the process to include adding a specific assignee. The assignee will act as a final reviewer and it is their responsibility to merge contributions to the repository.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [ ] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This change adds branch guidance for the creation of feature branches.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [ ] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
* add vscode settings and extension recommendations
* wrap markdown files at 90 columns
* add details for using VS Code workspace settings to contributing guide
Co-authored-by: Ibrahim Maga <imaga75@hotmail.com>
# Pull Request
## 📖 Description
<!---
Provide some background and a description of your work.
What problem does this change solve?
Is this a breaking change, chore, fix, feature, etc?
-->
This fixes an error in the `CONTRIBUTING.md` file where an extra space was added.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
Do you recommend a smoke test for this PR? What steps should be followed?
Are there particular areas of the code the reviewer should focus on?
-->
Attempting to use the suggesting yarn change api with the branch option did not work, removing the space fixes this therefore this update is to the contributing docs to remove the potential confusion for contributors.
## 📑 Test Plan
<!---
Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes.
-->
Try using the contributing docs yarn change api, see it will not point to the suggested branch and will revert back to master.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have included a change request file using `$ yarn change`
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project.
### Component-specific
<!--- Review the list and put an x in the boxes that apply. -->
<!--- Remove this section if not applicable. -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## ⏭ Next Steps
<!---
If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next.
-->
Co-authored-by: Aaron Wentzel <16669785+awentzel@users.noreply.github.com>
<!--- Provide a summary of your changes in the title field above. For guidance on formatting, see the comment at the bottom of this template. -->
# Description
<!--- Describe your changes. -->
This change adds an action that will lint the pull request titles to ensure the follow conventional commits. It also adds in some contributor documentation for dealing with merging PRs.
## Motivation & context
<!--- What problem does this change solve? -->
<!--- Provide a link if you are addressing an open issue. -->
Too many commits are going in without the proper commit messages, this will result in erroneous change logs as well as incorrect versioning.
## Issue type checklist
<!--- What type of change are you submitting? Put an x in the box that applies: -->
- [x] **Chore**: A change that does not impact distributed packages.
- [ ] **Bug fix**: A change that fixes an issue, link to the issue above.
- [ ] **New feature**: A change that adds functionality.
**Is this a breaking change?**
- [ ] This change causes current functionality to break.
<!--- If yes, describe the impact. -->
**Adding or modifying component(s) in `@microsoft/fast-components` checklist**
<!-- Do your changes add or modify components in the @microsoft/fast-components package? Put an x in the box that applies: -->
- [ ] I have added a new component
- [ ] I have modified an existing component
- [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition)
- [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration)
## Process & policy checklist
<!--- Review the list and check the boxes that apply. -->
- [ ] I have added tests for my changes.
- [ ] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
- [x] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/en/contributing/standards) for this project.
<!---
Formatting guidelines:
Accepted peer review title format:
<type>: <description>
Example titles:
chore: add unit tests for all components
feat: add a border radius to button
fix: update design system to use 3px border radius
<type> is required to be one of the following:
- chore: A change that does not impact distributed packages.
- fix: A change which fixes an issue.
- feat: A that adds functionality.
<description> is required for the CHANGELOG and speaks to what the user gets from this PR:
- Be concise.
- Use all lowercase characters.
- Use imperative, present tense (e.g. `add` not `adds`.)
- Do not end your description with a period.
- Avoid redundant words.
For additional information regarding working on FAST, check out our documentation site:
https://www.fast.design/docs/en/contributing/working
-->
* chore: change all instances of fast-dna to fast
* chore: revert cloudinary url changes
* chore: revert medium blog url change
* docs: fix some broken links in the intro
* update to improve speed of filing PR
* Revert "update to improve speed of filing PR"
This reverts commit 83c177ed77.
* update contributing documentation
* test conversion to yarn
* test updated yaml for circleci
* fixing builds
* update circleci to install via yarn docs
* setup prettier as global install for test
* use sudo to install lerna
* update typings for tooling package plugin controls
* fix component explorer issues
* doc updates
* fix angular tests with tsconfig
* test cache and frozen lockfile
* ensure workspaces are built
* change build to prepare
* fixing tests
* update component explore readme conversion path for node modules
* setup tests to stream again
* update working documentation
* update lockfile
* change back to npm from yarn install
* update readmes to reflect npm vs yarn
* revert tooling changes
* fix: updated typos, grammer and formatting for .md files and comments
* update to fix broken link
* Minor updates based on PR comments
* fix CONTRIBUTING.md merge issues
Jane Chu
Chris Holt
Aaron Wentzel
Steph
Dany Gagnon
Rob Eisenberg
John Kreitlow
Dexter Lesaca
Jazib Jafri
gpresland
Nicholas Rice
Jason Falk