Message343479
When developing on macOS, after some build/test operations (I'm not sure exactly which, but seemingly relating to a framework build), artifacts are generated which aren't ignored. As a result, it's easy for them to leak into a merge request as they did with GH-12547 (issue34632).
For example:
```
cpython master $ ./configure --enable-framework=/Users/jaraco/Library/Frameworks && make
...
cpython master $ git status
On branch master
Your branch is up to date with 'origin/master'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
Mac/Resources/app/Info.plist
Mac/Resources/framework/Info.plist
Python.framework/Python
Python.framework/Versions/
nothing added to commit but untracked files present (use "git add" to track)
```
(also Python.framework/Resources/, except that's in the repo at the moment, the reason for reporting this issue)
Is there not a reason to ignore these artifacts so they don't risk being added to the commit? |
|
Date |
User |
Action |
Args |
2019-05-25 13:58:32 | jaraco | set | recipients:
+ jaraco, ronaldoussoren, ned.deily |
2019-05-25 13:58:32 | jaraco | set | messageid: <1558792712.2.0.796235844945.issue37044@roundup.psfhosted.org> |
2019-05-25 13:58:32 | jaraco | link | issue37044 messages |
2019-05-25 13:58:32 | jaraco | create | |
|