Open
Conversation
Don't include binaries, publish them via Releases instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please Check The Preview
Add Tags
pcbgerber-filesdriver-boardcaseAdd Description
Miniature driver board, case & software.Disable unused Widgets:
PackagesDisable unused Tabs:
ProjectsActionsWikiSorted files
Removed binaries such as gerber files.
Don't include theses in the repository,
instead publish them via the
Releasesfeature.
Also don't version names of files in the
repository, that's what git is for, if you
want to preserve certain version of the
files, simply create a branch / tag.
Added quicklinks
Replaced license badge, added alt title
Added preview of the driver board
Transparent version would be preferred.
If you have any questions.
In case you do not agree with some of the changes made in this PR,
please first let me know about them, before disregarding it entirely so
we can possibly find a middle ground and have it not go to waste.
No, I'm not a robot.
Yes, you are not the first.
I just made a PR template.
If you are new to GitHub and aren't sure how to accept commits,
please familiarize yourself with the basics of Git / GitHub first.
Pull Requests
To accept pull requests you simply have to
press the Merge PullRequest button.
Never Copy-Paste Someones Contribution,
this robs them off their attribution and is thus
just plain copyright theft.
If you want to know more about Markdown check out: