You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is to notify the stakeholders of this repository (namely the developers contributing) that I intend to switch this repository to automatic formatting with black.
This will standardise the formatting of the project and it can be integrated with tox and CI to do so automatically.
Needless to say, this will introduce a large number of conflicts if there are PRs in progress since there's a high likelihood that many lines of code will change, I'm opening this and pinging people who will likely be impacted, namely @aliparlakci@OMEGARAZER@chapmanjacobd@Soulsuck24.
For anyone else who is currently developing, hopefully you either see this or it won't be trouble. For those that I have pinged or otherwise have a stake in the current codebase remaining static, please leave comments below so we can organise a timeframe for me to introduce this new part of the workflow in a way that won't cause too much disruption for anyone.
The text was updated successfully, but these errors were encountered:
This issue is to notify the stakeholders of this repository (namely the developers contributing) that I intend to switch this repository to automatic formatting with black.
This will standardise the formatting of the project and it can be integrated with tox and CI to do so automatically.
Needless to say, this will introduce a large number of conflicts if there are PRs in progress since there's a high likelihood that many lines of code will change, I'm opening this and pinging people who will likely be impacted, namely @aliparlakci @OMEGARAZER @chapmanjacobd @Soulsuck24.
For anyone else who is currently developing, hopefully you either see this or it won't be trouble. For those that I have pinged or otherwise have a stake in the current codebase remaining static, please leave comments below so we can organise a timeframe for me to introduce this new part of the workflow in a way that won't cause too much disruption for anyone.
The text was updated successfully, but these errors were encountered: