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

Let .templatesyncignore be inside .github folder #249

Closed
LuisHenri opened this issue Dec 13, 2022 · 8 comments · Fixed by #252
Closed

Let .templatesyncignore be inside .github folder #249

LuisHenri opened this issue Dec 13, 2022 · 8 comments · Fixed by #252
Labels
enhancement New feature or request
Milestone

Comments

@LuisHenri
Copy link
Contributor

LuisHenri commented Dec 13, 2022

Is your feature request related to a problem? Please describe.
I like to keep my root as clean as possible. Since .templatesyncignore file is something related to a github action, I guess it could also be stored in there.

Describe the solution you'd like
First search for it inside .github folder, then on root. I guess a simple IF...ELSE or so on the sync_template.sh would be enough

@LuisHenri LuisHenri changed the title let .templatesyncignore be inside .github folder Let .templatesyncignore be inside .github folder Dec 13, 2022
@github-actions
Copy link
Contributor

Hi! Thank you for your contribution!'Happy coding! 🚀

@LuisHenri
Copy link
Contributor Author

Perhaps same for .templateversionrc? Store it inside .github?

@AndreasAugustin
Copy link
Owner

Hi @LuisHenri thank you very much for the idea. Generally I like it.
With a fast google I did not find a spec currently what is allowed to go into the .github folder. I know at least some github actions (e.q. https://github.com/marketplace/actions/labeler). This is something I would like to clarify first if this is possible , but I think it is ok :)

@AndreasAugustin AndreasAugustin added the enhancement New feature or request label Dec 14, 2022
@AndreasAugustin
Copy link
Owner

@all-contributors please add @LuisHenri for ideas

@allcontributors
Copy link
Contributor

@AndreasAugustin

I've put up a pull request to add @LuisHenri! 🎉

@LuisHenri
Copy link
Contributor Author

Hi @LuisHenri thank you very much for the idea. Generally I like it. With a fast google I did not find a spec currently what is allowed to go into the .github folder. I know at least some github actions (e.q. https://github.com/marketplace/actions/labeler). This is something I would like to clarify first if this is possible , but I think it is ok :)

Hey @AndreasAugustin! Thank you for the feedback! With a quick google I also found this regarding .github folder: https://stackoverflow.com/questions/60507097/is-there-an-overview-of-what-can-go-into-a-github-dot-github-directory

Seems like it's a "normal" directory. Is there a way of testing any changes locally? I usually use Windows. But seems like I can test it on Docker, right?

@AndreasAugustin
Copy link
Owner

@LuisHenri about testing locally. Yes there are docker images available:

But it lacks documentation #254
Another option is that you just use the plain script src/sync_template.sh or also possible inside src/entrypoint.sh.
Related to the tests you want to do maybe that is a better option. (you can comment inside the script). In the end the docker container will also just call that script :)

@AndreasAugustin
Copy link
Owner

@LuisHenri I did not find any conventions or rules about the usage of .github/ folder. So lets go for the mentioned solution.

For the algorithm: lets give the .github/ folder more weight. That means that we will first search in the .github/ folder for .templateversionrc and .templatesyncignore files and use them if they are present. If one of the files is not present, we search this file in the root.

@AndreasAugustin AndreasAugustin added this to the v0.7.0 milestone Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

2 participants