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
Validation will only use the latest release version - not the branch I work in? #3428
Comments
Make sure you have read the issue guidelines and that you filled out the entire template. If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a 👍 reaction to the issue description. Thanks! 👍 |
It seems to be limited to the doc check, the rest is using the branch https://github.com/ExperienceLovelace/ha-floorplan/actions/runs/7385800876/job/20091413836#step:4:26 |
I've made a release with the README.md in the root folder, so the problem are not vislble in the master branch anymore, but the links are still showing the issue. Thanks ludeeus 😄 ! Sounds great. |
Describe the issue
I noticed that the validation would only work with the latest release, and not the branch I'm working in.
Debug output:
Here's the debug output where I'm working in a branch, not tired to any specific release.
I can see some work has been done related to #3362 in #3363, but I don't understand why the validation is tired to the latest release?
_I even ended up trying another README.md from
tonyroberts/scheduler-card/main/README.md
, before I noticed the debug-run option.As a developer I expected the run to validate the current repo. Not trying to fetch the latest release. I couldn't find anything related to that in the docs, so I'm not sure if I have missed something?
Have I originally implemented the validation it in a wrong way, or?
Link to action run
https://github.com/ExperienceLovelace/ha-floorplan/actions/runs/7385800876/job/20091413836
Link to action configuration
https://github.com/ExperienceLovelace/ha-floorplan/blob/hacs-verification-issues/.github/workflows/hacs-validation.yaml
Checklist
The text was updated successfully, but these errors were encountered: