-
Notifications
You must be signed in to change notification settings - Fork 119
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
Update for DDJ-200 4-deck mode #237
Conversation
Co-authored-by: Jan Holthuis <[email protected]>
Co-authored-by: Jan Holthuis <[email protected]>
Co-authored-by: Jan Holthuis <[email protected]>
Co-authored-by: Jan Holthuis <[email protected]>
Co-authored-by: Jan Holthuis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aligned table
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is easier to grasp.
Co-authored-by: Jan Holthuis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix the column alignment in the second table.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
columns aligned
Thanks. There are some pre-commit issues due to whitespace. Check the |
But the pre-commit errors don't seem related to my changes but to a Hercules controller. |
One of the pre-commit hooks that checks if the RST markup is valid.
Please do an pull the lastest |
Sounds complicated.
What do you want me to achieve?
|
It actually isn't. Just open a shell and run the following commands:
Then commit the merge and run:
|
… pioneer-ddj-200
Ok, I did it. There are no pre-commit issues. |
No, there was a issue present in the upstream branch when you forked. It was fixed upstream in the meantime, but the fix was not part of this branch. By pulling in the changes, we can now review this properly and know that this branch is pre-commit warning-free. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I think this ready to merge. One minor issue below.
Co-authored-by: Jan Holthuis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
Does it make sense to delete this repo and fork it from mixxxdj/manual in case of new contributions? |
No, you can keep it. If you want to make a new contribution, I suggest to use the If you don't have it (you can check with
Next time you want to contribute, you can just do:
|
Alright. Thank you! |
No description provided.