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

Define a project commit format #27

Closed
SoniEx2 opened this issue Jul 13, 2019 · 2 comments
Closed

Define a project commit format #27

SoniEx2 opened this issue Jul 13, 2019 · 2 comments

Comments

@SoniEx2
Copy link

SoniEx2 commented Jul 13, 2019

GAnarchy has this thing called a "project commit". It uses the following format:

[Project] {{Title}}

{{Description}}

Title may not contain newlines and Description may contain anything. However, I don't feel like it's worthwhile to keep it GAnarchy-specific. As such, I'd like to propose a common project commit format that anything can use. It would still follow the same basic structure, but we can adapt some things. We could add an YAML section or something, or define the description to be markdown-based, or so on. Maybe it should also be allowed to refer to any files available at the moment of the project commit, which would be useful for a project logo. This would benefit any tools doing anything even remotely like GAnarchy. I'd need to adapt GAnarchy to handle the new format, but if we stick to plaintext formats, it shouldn't be a big deal.

@techknowlogick
Copy link

Per #26 this repo is no longer the correct place to discuss forgefed, please refer to that PR for instructions on where the best place to discuss forgefed.

@SoniEx2
Copy link
Author

SoniEx2 commented Jul 13, 2019

oh. thanks. apologies.

@SoniEx2 SoniEx2 closed this as completed Jul 13, 2019
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

No branches or pull requests

2 participants