-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Do non-builtin styles work? #4
Comments
Yes, my intent is for all of Vale's features to work. You can see here that The linked PR doesn't reference |
Hmm, well I am utterly confused then, been playing with this for ages and getting nowhere… This is a test PR - https://github.com/kauri-io/Content/pull/109/files It's a bit more complex than your example, but as far as I can tell, it's correct, even with an empty folder to checkout remote styles (not sure that's needed). But as you can see all I get in that PR is Any insights would be appreciated as I feel like there's something really obvious I'm missing… Then I'll write some blog posts and docs 😁 |
I can't say that I completely understand why you're getting output from
If these changes don't help, I'll have more time to look into this next week. |
Ha! Not sure if it was removing the https://github.com/kauri-io/Content/pull/110/files It still keeps checking files that weren't changed, but I think that's more of an action configuration issue than a an issue with this specific action. Sometimes you just need a second pair of eyes… |
Though actually, if you look here - https://github.com/kauri-io/Content/pull/111/files Things are working, but too much is working, it's running tests that are specifically set to |
I've finally had a chance to look into this and, frankly, I'm still not exactly sure why you're seeing these results (Actions are somewhat difficult to debug and test). However, I did find and fix a potential race condition when there's no local configuration file (now I set up two test branches that emulate your repository's structure (two external styles, no local config file) and it's working as expected. |
@jdkato Still the same problem I'm afraid, with disabled default vale checks running even though they're disabled. Here's a couple of thoughts. The action uses Vale 2 beta, none of the styles I'm using have been tested with version 2, could that be an issue? Your test branches are using version 2, mine 2-beta.2, and yours output JSON style debug messages, and my output doesn't. i.e.,
mine:
Which is odd… But as you say actions are damned hard to debug… :( |
Interestingly if you look on this check (the Gah, actions have so much promise, but are too much of a black box 😩 |
I've just spent the last hour or so trying to get custom styles to work and I can't for the life of me get it to work either. My repo is here https://github.com/vendrhub/vendr-documentation using a fairly basic setup yet I have a rule here https://github.com/vendrhub/vendr-documentation/blob/master/.github/styles/Vendr/Terms.yml which should suggest "back-office" should be "backoffice", but this page is full of "back-office" https://github.com/vendrhub/vendr-documentation/blob/45ccd055909f8a5dc9e4ad83ade838687792ed3f/content/core/1.0.0/getting-started/installation.md and Vale is not showing any warnings about this https://github.com/vendrhub/vendr-documentation/runs/480670597 |
@mattbrailsford You need to include your style in your config file: You currently only have |
Ahhhh. Thanks, I’ll give that a try 👍🏻 Would be great if something like this could be added as an example as I was really struggling to find examples of setting up local styles properly. |
This is something I definitely have in progress, will finish it up asap. |
I was playing with adding the action to a repository, and while any of the inbuilt
vale
styles worked, nothing else did. So when I looked at the example you have here #1 I'm not actually sure that the nonvale
styles there work either.For example:
Should flag two write-good warnings, but there are none, even though , as far as I can tell write-good checks should be running.
The text was updated successfully, but these errors were encountered: