Support .giteapc subdirectory #8

Open
opened 2024-04-20 16:24:24 +02:00 by cake · 1 comment

Most tools that have a configuration within git repositories use hidden files or directories:

  • Gitlab CI uses .gitlab-ci.yml
  • Gitlab issue templates uses .gitlab/issue_templates
  • Gitlab merge request templates uses .gitlab/merge_request_templates
  • Pycharm uses .idea
  • EditorConfig uses .editorconfig
  • etc.

It would be great to have GiteaPC support the same, i.e. support .giteapc/giteapc.make and .giteapc/giteapc-config-<config>.make, instead of root-only, in order to "isolate" the GiteaPC configuration from the rest.

Most tools that have a configuration within git repositories use hidden files or directories: * Gitlab CI uses `.gitlab-ci.yml` * Gitlab issue templates uses `.gitlab/issue_templates` * Gitlab merge request templates uses `.gitlab/merge_request_templates` * Pycharm uses `.idea` * EditorConfig uses `.editorconfig` * etc. It would be great to have GiteaPC support the same, i.e. support `.giteapc/giteapc.make` and `.giteapc/giteapc-config-<config>.make`, instead of root-only, in order to "isolate" the GiteaPC configuration from the rest.
Owner

That's a great idea. I'm not sure when I'll have a cycle to spend on this, but now that I've seen it I want to make it the default.

That's a great idea. I'm not sure when I'll have a cycle to spend on this, but now that I've seen it I want to make it the default.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Lephenixnoir/GiteaPC#8
No description provided.