Skip to content
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

Dockerfile Naming Convention | Edge Case #1070

Closed

Conversation

sethbergman
Copy link

I was wondering if this would be useful in your project. I found that GitLab uses it and thought I'd attempt to contribute. I've since found a workaround for syntax highlighting in our Dockerfile_1.11.1 type naming convention. Let me know if I've missed something and I'd be happy to commit more to this awesome project!

@vidarh
Copy link
Contributor

vidarh commented Jan 21, 2019

@sethbergman There's another one that covers parts of this (#1059). I think once #1062 (to fix the CI) has been sorted out, we should make sure to look at solving both of these cases too. Just waiting for one of the maintainers to have time to get those earlier bits cleared out.

@sethbergman
Copy link
Author

@vidarh thanks for the update!

Removed specific bundler version
@pyrmont
Copy link
Contributor

pyrmont commented May 28, 2019

@sethbergman Sorry it's taken a while to get back to you on this :( Would you be able to do force push to kick off a fresh CI cycle?

You should be able to do something like:

$ git commit --amend
$ git push --force

@pyrmont pyrmont added the author-action The PR has been reviewed but action by the author is needed label May 28, 2019
@pyrmont pyrmont closed this in 4e5e248 May 28, 2019
@pyrmont pyrmont removed the author-action The PR has been reviewed but action by the author is needed label May 28, 2019
@pyrmont
Copy link
Contributor

pyrmont commented May 28, 2019

@sethbergman Sorry for the flood of notifications! A similar PR, #1059, has incorporated your tweaks and been merged in. Thanks for your help!

@sethbergman
Copy link
Author

@pyrmont that's great! Thanks for letting me know!

pyrmont added a commit that referenced this pull request Jul 4, 2020
In addition to adding the `*.Dockerfile` file glob, #1059 added a file
glob for `Dockerfile_*` to address #1070. However, as noted by #1539,
this causes issues for files that begin with `dockerfile_` but that are
not Dockerfiles.

Adding the `Dockerfile_*` file glob was an error and this commit
removes it. It is a non-standard name and is not recognised by other
syntax highlighting libraries (e.g. Pygments, Chroma, Linguist). The
correct fix for the issue that precipitated #1070 is to use a
`.gitattributes` file.
mattt pushed a commit to NSHipster/rouge that referenced this pull request May 19, 2021
In addition to adding the `*.Dockerfile` file glob, rouge-ruby#1059 added a file
glob for `Dockerfile_*` to address rouge-ruby#1070. However, as noted by rouge-ruby#1539,
this causes issues for files that begin with `dockerfile_` but that are
not Dockerfiles.

Adding the `Dockerfile_*` file glob was an error and this commit
removes it. It is a non-standard name and is not recognised by other
syntax highlighting libraries (e.g. Pygments, Chroma, Linguist). The
correct fix for the issue that precipitated rouge-ruby#1070 is to use a
`.gitattributes` file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants