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

Standard code formatting for TOMToolkit #1177

Open
3 tasks
phycodurus opened this issue Feb 12, 2025 · 1 comment
Open
3 tasks

Standard code formatting for TOMToolkit #1177

phycodurus opened this issue Feb 12, 2025 · 1 comment
Labels
maintenance Non-user facing updates to clean code and make developer life easier. Patch Party Collaborative effort mostly done as part of a patch party

Comments

@phycodurus
Copy link
Contributor

phycodurus commented Feb 12, 2025

Developer life quality might be improved by standard code formatting across TOMToolkit repos:

  • using Ruff or Black or ??,
  • with a commit hook?,
  • without clobbering the git blame history?,
@phycodurus phycodurus moved this to Triage in TOM Toolkit Feb 12, 2025
@phycodurus phycodurus added the maintenance Non-user facing updates to clean code and make developer life easier. label Feb 12, 2025
@jchate6
Copy link
Contributor

jchate6 commented Feb 14, 2025

Have git ignore primary formatting commit for purposes of blame.

@jchate6 jchate6 added the Patch Party Collaborative effort mostly done as part of a patch party label Feb 14, 2025
@jchate6 jchate6 moved this from Triage to Backlog in TOM Toolkit Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Non-user facing updates to clean code and make developer life easier. Patch Party Collaborative effort mostly done as part of a patch party
Projects
Status: Backlog
Development

No branches or pull requests

2 participants