-
Notifications
You must be signed in to change notification settings - Fork 7
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
Refactor to align with template-formula; fix failures #29
Refactor to align with template-formula; fix failures #29
Conversation
BREAKING CHANGE: Major refactor of formula to bring it in alignment with the . As with all substantial changes, please ensure your existing configurations work in the ways you expect from this formula.
c8f1bfa
to
7622aea
Compare
7622aea
to
affbe43
Compare
* Automated using myii/ssf-formula#177
```bash $ yamllint -s . ./eclipse/defaults.yaml 55:89 error line too long (120 > 88 characters) (line-length) ./test/salt/javascript/pillar.sls 34:89 error line too long (144 > 88 characters) (line-length) ./test/salt/java/pillar.sls 5:89 error line too long (92 > 88 characters) (line-length) 33:89 error line too long (134 > 88 characters) (line-length) ./test/salt/cpp/pillar.sls 34:89 error line too long (144 > 88 characters) (line-length) ```
Best reviewed: commit by commit
Optimal code review plan (1 warning)
|
@noelmcloughlin Finally, review this one and pushed two commits on top to standardise the structure. Please have a look at both and go ahead and merge if you're OK with the proposed changes.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @myii for reviewing
@noelmcloughlin There's another |
https://travis-ci.com/github/saltstack-formulas/eclipse-formula/jobs/328737888#L303-L305 $ yamllint -s .
./pillar.example
25:18 warning too few spaces before comment (comments) |
Forcing the |
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?Yes,
but the existing formula is not working anyway
Related issues and/or pull requests
The formula was failing because the hardcoded 2018 release is no longer available - see
#28. This PR fixes that issue and is a rewrite to align to template-formula. Travis is passing for various Linux.
Describe the changes you're proposing
Refactored formula
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context