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

Library is required to be in the "master" branch of the github repo. #14

Open
zfields opened this issue Jun 1, 2015 · 2 comments
Open

Comments

@zfields
Copy link
Contributor

zfields commented Jun 1, 2015

You require the library to be in the master branch of the github repo. This isn't very conducive to existing repositories. I actually had to mangle the master branch of my existing library.

Could you guys give the option or make another rule to pull from a "spark" branch? It would allow me to make a commit that flattens my folder hierarchy, and a second that corrects my header inclusions. Then I could simply rebase those changes onto my master branch and leave them in the spark branch.

@zfields
Copy link
Contributor Author

zfields commented Jun 1, 2015

This issue was valid as of 2015/02/16. I'm cleaning my inbox and translating all my notes into issues.

@embedded-creations
Copy link

I agree with this feature request, and add that the README should mention that the "master" branch is the only branch that can be used. When trying to validate a library with Particle Build, it just displays a blank screen when there is no master branch.

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