I believe this was resolved by D20327 / D20393.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 27 2019
I believe this has been fixed by D20327 / D20393 -- at least, the examples above no longer seem to reproduce any bad behavior.
Apr 25 2019
Please use the Discourse forum for this kind of discussion.
Apr 24 2019
Apr 23 2019
(This seems stable now, and there's no specific action here.)
In PHI1008, when commit X reverts commit Y, we don't write a revert edge between X and revisions associated with Y. We should.
Apr 22 2019
Leaving the "Assign To: [...]" field blank will remove assignees, but this is not obvious:
Apr 20 2019
I believe there is very little reason for the "Autoclose" and "Publish" behaviors to actually be separate. That is, there are very few use cases where users want a commit to trigger only Herald or only feed or only audits. These use cases do exist (see T9210 for an example of "Herald, No Feed") but they're overwhelmingly niche and off-label.
Apr 19 2019
Apr 18 2019
This could be made slightly cleaner with a setSummary() to set a shorter summary:
The git fetch change in D20421 does actually affect non-bare repositories:
This is expected: the revision is not newly created.
This is expected: the revision is not newly created.
hmmmmmm
Apr 17 2019
Apr 16 2019
APIs: Currently, diffusion.repository.search does not expose staging information.
When there are no refs in a repository, the server does not appear to send a capabilities frame:
Empirically, on modern git:
Apr 15 2019
This is a duplicate of T8936 and resolved by D20420.
D20433 deprecates "Track Only", mooting this.
After D20420, we accept these refs.
D20420 accepts these refs. We don't show notes in the UI, but we have no outstanding customer requests for this.
See T13277. I'm moving us away from "Track Only", and our behavior is already reasonable under "Fetch Rules" + "Permanent Refs".