16 Commits (dev_version_changes)

Author	SHA1	Message	Date
Wilken Rivera	699c0f814c	Update plugin_integration.md ... Fix todo list markdown formatting	2 years ago
Wilken Rivera	c0de07c32e	Document process for registering a plugin as a Packer Integration	2 years ago
hashicorp-copywrite[bot]	19055df3ec	[COMPLIANCE] License changes (#12568) ... * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at https://hashi.co/bsl-blog, FAQ at https://hashi.co/license-faq, and details of the license at www.hashicorp.com/bsl. * Update copyright file headers to BUSL-1.1 --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
hashicorp-copywrite[bot]	b7df3ca36f	[COMPLIANCE] Add Copyright and License Headers (#12254) ... Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
Lucas Bajolet	08157fbdce	Add workflow to link to discuss on new question (#11825) ... * workflows: + automatic label/response on question When a user asks a question through an issue on this repository, we automatically add a comment, pointing to the forums, and add a label to the issue so we can spot more easily which issues need to be acted on. * .github: + link to packer community for questions As extra to the github action, this commit adds an extra button to the new issue template, leading directly to the discuss forums for Packer * .github: add auto-stale-close issue action As follow-up to the labelling of question type issues as needs-reply, we add another action that will automatically mark an issue as stale if it has not been updated for 3 weeks, and close the issue one week after marking it as stale. * Update .github/workflows/issues-opened.yml Co-authored-by: Wilken Rivera <wilken@hashicorp.com>	4 years ago
Wilken Rivera	e2dc5a7137	Update community note on GitHub issue templates (#11715) ... 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.	4 years ago
Kerim Satirli	bc6f1e36e6	Fixes typos in docs (#11322) ... * 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	4 years ago
Adrien Delorme	d31192a7fc	Update feature_requests.md ... add a 'Community Note' section	6 years ago
Jeff Escalante	9165be87da	packer.io prefix removal, html extension remove for in-code errors	6 years ago
Adrien Delorme	3951267963	Create ssh_or_winrm_times_out.md	7 years ago
Adrien Delorme	0fcc4688f1	default labels per ISSUE_TEMPLATE type	7 years ago
Megan Marsh	211f7bd9de	fix formatting	7 years ago
Megan Marsh	bcb7d1e103	fix formatting	7 years ago
Megan Marsh	00f97e871c	clean up bug report template	7 years ago
Adrien Delorme	a204a14973	Update question.md	7 years ago
Adrien Delorme	9a4932e831	split issue templates: bug report/enhancment/question ... so that people are routed nicely :)	7 years ago