Quest runs nightly, rather than on each label update.
The following changes make that happen:
- The bulk action runs once a day, at a hopefully convenient time.
- The single item workflow runs only in response to a workflow dispatch event (user started)
- For security reasons, limit the permissions to write *issues*, not *contents*
We've added the source to the what's new tool to the dotnet/docs-tools repo.
That let's us update this action to pull directly from that repo, and automatically pick up any of the latest fixes when it runs.
* update whats new file names
Rename all the existing files to match the new names. Then, update the TOC, index, and redirections to match the new names.
* remove old NuPkg
* Add latest NuPkg
* Fix redirection targets.
* Redirection, part II
* Add config for Quest import
This PR adds the configuration for the Quest import GitHub action.
Before merging this PR, follow the instructions [here](https://github.com/dotnet/docs-tools/tree/main/actions/sequester#installation-and-use) to create the API KEY secrets. Then, once this is installed, it will start updating work items.
Note: To import items in bulk, when those have already been labeled, you can run the `quest-bulk` action via the GitHub UI to import all issues already labeled.
* better filter.
* Update .github/workflows/quest-bulk.yml
Co-authored-by: David Pine <david.pine@microsoft.com>
Co-authored-by: David Pine <david.pine@microsoft.com>
- Update the NuPkg to 2.1.2.
- Update the installed .NET SDK to 6.0
The new package requires the latest .NET SDK. The new package uses the OSPO query for organization membership instead of GitHub organization membership.
- Add shell script, yml config and package for "what's new" package
- add the NuGet package with the latest tool
- Update the whatsnew.json file to include parameters for automatically updated the index.yml and toc.yml
- Update the TOC so that it has a single rolling list of articles (the action expects that)