Any concerns about landing those changes? Once I land I'll see about updating this instance which should make accessing the repositories possible again.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
May 21 2022
May 21 2022
May 20 2022
May 20 2022
Merged the arcanist repository in D25039
May 17 2022
May 17 2022
This would be a legitimately good exercise to try and do "properly"... although, the thought of not doing it optimally can be a bit of a barrier to starting..
Here is one thing I noticed... In at least a couple of the files, there may be changes that:
May 12 2022
May 12 2022
If we merge, a force-push should not be required - unless you mean something other than standard git merge here. (Force-push is required when rewriting already pushed history - git merge simply adds a new commit that applies the changes on top of the branch)
May 3 2022
May 3 2022
It looks like upstream has issued a number of updates which we'll want to pull in. From {E4} we discussed doing the following:
Apr 20 2022
Apr 20 2022
Created {D25036}
Apr 19 2022
Apr 19 2022
Apr 5 2022
Apr 5 2022
Mar 16 2022
Mar 16 2022
Feb 25 2022
Feb 25 2022
Feb 7 2022
Feb 7 2022
Sep 22 2021
Sep 22 2021
Sep 4 2021
Sep 4 2021
Aug 26 2021
Aug 26 2021
Aug 24 2021
Aug 24 2021
Aug 23 2021
Aug 23 2021
Aug 19 2021
Aug 19 2021
Aug 18 2021
Aug 18 2021
Jul 27 2021
Jul 27 2021
Jun 21 2021
Jun 21 2021
Jun 12 2021
Jun 12 2021
Jun 11 2021
Jun 11 2021
Matthew added members for Trusted Contributors: willson556, cburroughs, jupe, tobiaswiese, Leon95, deadalnix.
Jun 10 2021
Jun 10 2021
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0