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

Storing built copies in the repository makes it hard to keep a fork #116

Open
akatrevorjay opened this issue Mar 9, 2018 · 1 comment
Open

Comments

@akatrevorjay
Copy link

akatrevorjay commented Mar 9, 2018

Hi. Love what you've done here.

I run my extensions locally and I pick a time that I update them all as I see fit.
In this case,. I even have a couple personal changes, nothing big. I also don't want them to auto update, so I update the application IDs in the manifest.

Unfortunately, it makes it hard to git pull from any fork when the build extension contents are stored in the repo.

Would you be against at least adding that to gitignore? That way I can at least pull without writing a shitty script around git to ignore those files. Gross ;)

@akatrevorjay
Copy link
Author

Oh, actually, this doesn't store the built exts (many do, sorry!)

The manifests however, would you be okay with a PR to make those generated from a template instead of putting them /extensions/{browser}?

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

1 participant