-
-
Notifications
You must be signed in to change notification settings - Fork 128
Feature/add dockerfile support #266
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
Conversation
i tried to run the tests, but they just kept getting stuck on my local machine, i assume they pass as its very simple but just an fyi |
There were just a few things to tweak (e.g. comments missing The remaining failure I'm not entirely sure about myself. It's related to URL insertion, and for some reason the action can't create a simulated version of the Dockerfile (perhaps due to no extension?). @rgalonso might be able to shed some light at some point, but I don't think this is crucial, so probably easiest to block it with |
I'm really confused about what's going on here. This PR says it was merged (specifically with commit cd4d0b0), but I don't see the changes on master and that commit says its not on any branch. @alstr, did your commit setting As to the issue you asked me to look into, I don't have an answer yet since I'm having trouble seeing the files in question. |
We ran into a few problems. The issue stems from a merge conflict that occurred when I manually merged this PR on GitHub and then attempted to push some other changes locally, which led to a few inconsistencies in the commit history. As a result, I had to rebase, which cleaned up the history back to 93316d1, but also removed this PR, apologies. I'll re-add it manually. |
Okay, I think we're back at the point we were at earlier, with the issue here: https://github.com/alstr/todo-to-issue-action/actions/runs/14382244288/job/40328706038 Apologies for the confusion, with the changes I made to the PR here, the merge and then the stuff I had locally, things just got a bit muddled. |
I figured out the issue with
This is due to an inconsistency in the path to
As you can see, in the first line, it says the path is The solution is to make sure the paths in those two lines match. Also, what's that's been done, you'll need to bump the number of expected passing tests from 79 to 80 in the |
I made those updates and it doesn't seem to have fixed the test: eded387 😕 |
Yeah, I see that. I think it fails to create the |
Weird. I don't think it's a big deal currently. I figured out why the test wasn't skipping (workflow file setup) so that'll do for now. |
New Language Definition Contribution
Thank you for contributing a new language definition! Please follow the guidelines below to ensure that your contribution can be easily reviewed and integrated into the project.
Description
Dockefile
Fixes #265
Checklist for Adding a New Language
Before submitting your pull request, please ensure the following requirements are met:
syntax.json
with the language name matching that in GitHub's Linguistlanguages.yml
file.test_new.diff
andtest_closed.diff
.test_todo_parser.py
. The tests should check that theace_mode
of the issue matches that specified in thelanguages.yml
file. If existing checks for thatace_mode
exists, I have incremented them instead.README.md
to add the language.Thank You
We appreciate your time and effort in improving this project!