# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
The build gate must pass for `gh-pages` branch, this update adds that branch to the workflow file.
## ✅ Checklist
### General
<!--- Review the list and put an x in 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.
## ⏭ 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.
-->
- Merge this change into the `gh-pages` branch
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
This pull request includes the previously reviewed work:
- #161
- #165
- #166
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
-->
These changes require a review and sign off as they are going into the `main` branch.
Co-authored-by: William Wagner <44823142+williamw2@users.noreply.github.com>
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
This change should add the wasm package to the build gate and prevent errors from being pushed. The package is currently private and requires `wasm-pack` to run.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
-->
The build gate should pass and include the tests in the wasm package. To run locally, follow the steps in the CONTRIBUTING.md file for the wasm package.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [x] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
Due to the face that the default `GITHUB_TOKEN` available to GitHub actions cannot push commits to protected branches, a new PAT has been added to the repository and referenced in the workflow. This should allow publish commits and tags to be pushed by the workflow.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
-->
The documentation from GitHub indicates that for extra permissions, this is the only solution, see https://docs.github.com/en/actions/security-guides/automatic-token-authentication#granting-additional-permissions
The permissions that the `GITHUB_TOKEN` does not cover includes git actions such as pushing commits, so there is no way to grant the generated token write access.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [x] I have updated the project documentation to reflect my changes.
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
According to the top answer https://stackoverflow.com/questions/63733822/cant-push-to-protected-branch-in-github-action with this same error we are seeing with the validator, the actions/checkout@v2 may be overriding the git permissions we have set up. This could be causing the error when attempting to push commits to the main branch.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have added tests for my changes.
- [ ] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
The build gate must have a `main` branch available to check against when assessing if change files need to be present. This accomplishes this by setting the fetch depth to 0, which will during checkout, check all branches out for reference.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
-->
See: https://github.com/actions/checkout#checkout-v2
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
This adds an additional check during the build gate validation to ensure that the build gate will not pass for a pull request if change files are required.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
-->
This should use the same step as the publish workflow.
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
Due to the updates needed for beachball to ensure a good workflow process for publishing, the `release` branch is renamed to `main` and pull requests must now be merged to `main`.
Refer to https://github.com/microsoft/fast-tooling/issues/78 for more details.
## 👩💻 Reviewer Notes
<!---
Provide some notes for reviewers to help them provide targeted feedback and testing.
-->
Consider if there are any other locations where the `release` branch is referenced which should be changed to `main`.
## ✅ Checklist
### General
<!--- Review the list and put an x in 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.
## ⏭ 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.
-->
# Pull Request
## 📖 Description
<!--- Provide some background and a description of your work. -->
This change affects the build gate and uses `npm ci` which installed from the package-lock file and should be more performant. More information about `npm ci` can be found [here](https://docs.npmjs.com/cli/v6/commands/npm-ci).
## ✅ Checklist
### General
<!--- Review the list and put an x in the boxes that apply. -->
- [ ] I have added tests for my changes.
- [x] I have tested my changes.
- [ ] I have updated the project documentation to reflect my changes.
* Create ci-fast-tooling.yml
* change ci title
* add build steps
* add test
* add npm prepare
* only install process in build
* npm run build if present
* remove test
* add npm 7 build
* change node version to 16
* add caching
* change tittle for naming convention
* add caching path
* seperate build and test task for time management
* seperate build and test task
* rm npm run build if present
* fix yml syntax
* Update .github/workflows/ci-fast-tooling.yml
we can try that also. it doesn't harm
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
Co-authored-by: Jane Chu <7559015+janechu@users.noreply.github.com>
Jane Chu
Aaron Wentzel
Ibrahim Maga
William Wagner