forked from cloudposse/build-harness
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge upstream #3
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update Slash Command Dispatch GitHub Actions templates * Update Slash Command Dispatch GitHub Actions templates * Update Slash Command Dispatch GitHub Actions template
Thanks! Makes sense...
* fix gomplate install * rebuild readme * Update README.md (cloudposse#201) Co-authored-by: osterman <osterman@users.noreply.github.com> Co-authored-by: Cloud Posse Bot (CI/CD) <ops@cloudposse.com> Co-authored-by: osterman <osterman@users.noreply.github.com>
* fix dispatch template paths * remove duplicate target
* Use github actions to build and push * Update readme * rename to docker * rename to docker * update descriptions * build-and-push * Update readme * more renaming * Update .github/workflows/build-and-push.yml Co-authored-by: Andriy Knysh <aknysh@users.noreply.github.com> Co-authored-by: Andriy Knysh <aknysh@users.noreply.github.com>
* add test workflow * bump versions * add test command * rename to chatops
* Fix assert-set * Update description * use native make to test variables * reenable deps-dev * use native make error handling
* MD changes to pass linting * Additional changes * Built readme * CR changes * Create ignore file by default * Change description to better match docs/deps * Change linter ignore to according type * Fix MD040/fenced-code-language lint error * Ignore just part of violating MD file * Ignore MD041 for whole file targets.md * Ignore linting all docs/*.md files
…oudposse#232) * Update README template to pass lint In PR against `terraform-example-module` I ran into [issue with superlint](https://github.com/cloudposse/terraform-example-module/pull/3/checks?check_run_id=928328375) > ERROR:[README.md:240 MD046/code-block-style Code block style [Expected: fenced; Actual: indented]] Here is documentation about it: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md046---code-block-style * Additional fix for another lint failure * Convert licenses to code and add superlint to gh actions * Fix readme * Remove ending white characters'
* use labels * fix auto labels
* update chatops permissions * update chatops * Update .github/workflows/chatops.yml Co-authored-by: Nuru <Nuru@users.noreply.github.com> * Update .github/workflows/chatops.yml Co-authored-by: Nuru <Nuru@users.noreply.github.com> * update slash-command-dispatch Co-authored-by: Nuru <Nuru@users.noreply.github.com>
* Fix module upgrade script * update deps
* terraform/migrate-to-registry Makefile target added * target renamed * readme rebuilded * markdown linter rules fix to avoid raising errors for lines longer then 400 chars * full linter config applied * terraform format for examples as well * markdownlint disabled for contributors table * regex fix * readme fix * readme fix * linter rules removed, no need for them any more
* mergify rule to close PRs without changes * Update templates/terraform/.github/mergify.yml Co-authored-by: Erik Osterman (CEO @ Cloud Posse) <erik@cloudposse.com>
…efore most of nightly build fires (cloudposse#281)
* Better formatting of combined release notes
* add conditional * fix formatting * update readme * Auto Format Co-authored-by: cloudpossebot <11232728+cloudpossebot@users.noreply.github.com>
…into cloudposse-master
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ray-harris The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.