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

KiCAD diff between two branches or at least between two tags or at least between two commits #17

Open
rusefillc opened this issue Aug 14, 2020 · 4 comments

Comments

@rusefillc
Copy link
Contributor

https://github.com/rusefi/hw_microRusEfi/branches has branched of the most important (for me :) ) actively developed PCB

which we already have the script for automated per-commit diffs, a different use-case is a diff between two historic revisions that case should probably be a command line tool?

if we place script inside https://github.com/rusefi/kicad-libraries/ we would have it in https://github.com/rusefi/hw_microRusEfi/ via existing submodule reference

@chuckwagoncomputing
Copy link
Member

What else would get it? I don't think we need it for this repo, as the only kicad_pcb files are outlines.

@chuckwagoncomputing
Copy link
Member

Actions can be set up to run on release. That would work for repos that contain one piece of hardware.

@rusefillc
Copy link
Contributor Author

https://github.com/rusefi/hw_microRusEfi has two boards - MRE and MRE test fixture
https://github.com/rusefi/hw_55_te would be one of public PnP boards
and a couple private PnP boards which are similar to https://github.com/rusefi/hw_55_te in terms of layout

@chuckwagoncomputing
Copy link
Member

With having more than one file per repo, I think having a version.txt file will be the best option.
Actions can be run on changes to particular files. I think we'd have to have an action for each board on a repo, unless I can come up with something better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants