Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U066LC126>: You are going to make that an option? Our users don’t have perms to write to /var/run by default.  Also the directory versioning will be a challenge. our jenkins builders have multiple copies of the repo checked out.  We attempt to shutdown all nailguns at the end of a ci run, so usually this isn’t a problem. Our ci builders usually run for a day and  are re-imaged in the morning when they come back up.

additionally OSX also doesn’t support writing there

maybe we could just beef up the name checking

I don’t think it’s an issue for our CI, but end users run into it intermittently

I think making the name checking better would cover the 99% case

The only corners are when the user has moved the repo to a different directory AND managed to kill pants in the previous run without giving it a chance to clean up its pidfile

FYI I'm going to be closing old, apparently abandoned pull requests.

We should publicize the trick for auto-closing PRs and encourage it

I don't remember what that trick even is.

this maybe? <https://help.github.com/articles/closing-issues-via-commit-messages/>

This is harder to do for people who don't have push privs, but not impossible

(1) Finish your CR, make sure the description etc is exactly how you want it, you have your ships, you're ready to push

(2) Checkout master, get it up to date with upstream, and use `./rbt patch -c` to make your commit

(3) `git push -f &lt;your GH fork remote&gt; master:&lt;your PR branch&gt;`

If you lose the race on 4, pull, then repeat steps 3 and 4

If the SHA of the HEAD of your PR branch matches the NEW SHA of the branch the PR is tracking against when the latter branch is updated, GH will automatically close the PR as "merged"

It looks nicer and you don't have to close it yourself

And instead of being marked as "closed" it's marked as "merged"

In your description `origin` is <http://github.com/pantsbuild/pants|github.com/pantsbuild/pants>? My `origin` is my fork, and `pantsbuild` is my other remote.

Makes me less likely to push -f to pantsbuild/pants by mistake...

I was trying to simplify, I am also tricky like that

I have `upstream` (pantsbuild/pants) and `pl` (pl/pants)