You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
Upon rubberstamp:revert the designated lines should be removed from .gitignore
NOTE - Verify this actually is true, lol
The text was updated successfully, but these errors were encountered: