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.

Sign up for GitHub

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

Jump to bottom

Standardize formatting #157

Closed
chrehall68 opened this issue Jun 27, 2022 · 2 comments
Closed

Standardize formatting #157

chrehall68 opened this issue Jun 27, 2022 · 2 comments

Comments

@chrehall68
Copy link
Contributor

Formatting is kinda inconsistent...

I suggest there be a standard ruleset. It could be explicitly put in the readme in a separate section marked 'formatting'.
@Zacharyprime
Copy link
Member

Zacharyprime commented Jul 25, 2022 •
edited
Loading

What exactly do you mean by formatting?

As in function/variable naming? Documentation? Issues? maybe CI/CD flow?

Not that I disagree, there are just a lot of contexts that your statement would make sense in.

@Zacharyprime
Copy link
Member

I'm still not sure what this meant.
This issue is too broad to represent any specific goal so I am going to close it.

If this is still a problem, feel free to create a new issue but please be specific or give a metric for what it would mean to accomplish the goal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Zacharyprime @chrehall68