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

Automate .gitignore handling #30

Open
GantMan opened this issue Jul 17, 2013 · 1 comment
Open

Automate .gitignore handling #30

GantMan opened this issue Jul 17, 2013 · 1 comment

Comments

@GantMan
Copy link
Member

GantMan commented Jul 17, 2013

When rubberstamp is installed and the _base files are generated, the stamped versions should be added to the .gitignore file so it doesn't nag and cause binary merge conflicts.

resources/Icon-72.png
resources/[email protected]
resources/[email protected]
resources/[email protected]
resources/Icon.png
resources/[email protected]

Upon rubberstamp:revert the designated lines should be removed from .gitignore

NOTE - Verify this actually is true, lol

@mattsgarrison
Copy link
Contributor

If someone already had icons in place and committed to their repository before adding motion-rubberstamp this would need to remove the original icons from the repository for the gitignore entries to be observed. While I don't think it's overly invasive to add and remove lines to a gitignore file, altering someone's existing repository could be an unwanted surprise.

Perhaps if no icons exist yet, we could add the gitignore entries. I'm not really keen on invoking git commands for the user, people are really picky about their git workflows.

Thoughts?

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

No branches or pull requests

2 participants