To assist in tracking newly created issues and pull-requests a new set
of actions is being added to assign inbound request to a new project
board. Where the team can view, filter, and organize in bound requests
across all Packer repos.
The Markdown link checker currently deployed has served its purpose for
the time being. It is being removed to avoid failed checks on PRs, while
we evaluate alternative solutions used by other HashiCorp repositories.
In an effort to help prioritize issues (i.e bugs and feature requests) that are important to the community
the community note pertaining to issue voting has been moved to the top of each
template with a comment informing users not to delete it. The goal is to
rely more on votes for feature requests and issues that are not critical.
Critical issues being crashes, regressions, security vulnerabilities, and broken features.
The latest release of the action requires the field
enable_versioned_regex to be set. We currently don't use
versioned_regex. So this change sets the field to false.
* Add tests for plugins install command
* Add tests for plugins remove command
* Add PACKER_GITHUB_API_TOKEN to all test env
* Update dir hashes for non-darwin os
* Update tests with feedback from review
In reviewing the results of the nightly release workflow it was found
that upon creating the release it was successfully marked as a
prerelease. But it still needed to be manually publish as an official
prerelease. This change adds a new action to publish the created
release, as the last step.
* fixes typos in base docs
* fixes typos in example code
* fixes typos in website docs
* fixes link to Terraform provider
* fixes typo in function name
This changes removes the use of HashiBot for migrating issues labels
with remote-plugin/* to their respective plugin repositories. The GitHub
action has feature parity with HashiBot so the migration should work as
it did before.
The GitHub action closes the original issues and creates a new issue on
the remote plugin repository with the original contents of the issue to
preserve history. We chose not to go with GitHub's issue transfer option
because it completely moves the issue to the target repo, meaning there
is not history that it was ever created on the original repository.
In the future, we will look to add an action for closing remote-plugin
issues that we no longer have access to.
Closes: #11043
* website: bump to docs-page prerelease with hidden page support
* website: remove temporary check for hidden pages, now covered by docs-page
* website: bump to stable docs-page, w next-mdx-remote bump
* website: bump to latest markdown-page
* Test against deployment url
* Remove infinite redirect configuration
* Add DEPLOYMENT_URL for builds against master
* website: Update README
* tip on seconds
* Test with GHA timeout_minutes clause
* Add continue on error for poll job
* Add empty url check
* Move to pull-request path filter
* Remove www for packer.io
* Apply suggestions from code review
* Update path filter
Vercel deploys on any change under the website directory.
* Use custom action as test
Co-authored-by: Adrien Delorme <[email protected]>
Wilken Rivera
Michele Degges
dependabot[bot]
Bryce Kalow
Adrien Delorme
Kevin Wang
Jenna Goldstrich
Kerim Satirli
Matthieu MOREL
Zachary Shilton
Sylvia Moss
Megan Marsh
Adrien Delorme
Wilken RiveraandAdrien Delorme