search for: phacil

...st command run locally. If indeed the arc > command requests the commit message from the server, I assumed so too until I went digging for it. Seems the client-side stuff only deals with the structured data, and calls out to the server to construct the raw text when needed: https://github.com/phacility/arcanist/blob/33b9728b5f65fd747b7a15c0e25436c63e82f592/src/workflow/ArcanistDiffWorkflow.php#L757 > we could do some > additional things: > > * Remove "Summary:" in front of message > * Line break after 72 columns > * Convert summary markdown formatting to plain...

Can we fix this in reviews.llvm.org's fork of phab? https://github.com/phacility/phabricator/blob/cac3dc4983c3671ba4ec841aac8efac10744a80c/src/applications/differential/conduit/DifferentialGetCommitMessageConduitAPIMethod.php Seems straightforward(-ish) to drop the relevant fields there, that way `arc land` automatically DTRT. Jon On Fri, Dec 27, 2019 at 11:30 PM Mehdi AM...

...b review is frustrating in comparison to phab, in particular the way comments are handled across updates, unless you stick to never rebase and only append commits and merges from master. This is unfortunately not compatible with the LLVM repo history right now. >>> >>> https://www.phacility.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.phacility.com&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=lJwxc7o34UKit8nM2fj4O0ASyu1JnOqeXvhr24fX66Y&s=9P-x7k7eVVMR4DlfgeXAq8p-1R_cVMVqOek61HN60Ho&e=> offers hosting for Phabricator, coul...

...urrently: > ~$300-350 / mo for sendgrid (300-350k emails / month) > ~$2k / mo for cloud (we currently run on 1 machine O.O, plus storage & > backup) > > If y'all care about the workflow but don't care about diffs in emails, we > can switch to stock phab. > I can ask Phacility for a quote; stock phab comes with significantly > different emails though. > I think it is a flat $12k/year above 50 users? (see: https://www.phacility.com/pricing/ ) > > Re: patch chains - perhaps we can ask github on support for that? > I think what would help is somebody pr...

...urrently: > ~$300-350 / mo for sendgrid (300-350k emails / month) > ~$2k / mo for cloud (we currently run on 1 machine O.O, plus storage & > backup) > > If y'all care about the workflow but don't care about diffs in emails, we > can switch to stock phab. > I can ask Phacility for a quote; stock phab comes with significantly > different emails though. > > Re: patch chains - perhaps we can ask github on support for that? > I think what would help is somebody providing a doc with the features that > phab provides that github PR doesn't, so we can get...

...d as Ticketing platforms for bug pull requests on the R-devel Git Repository. ? Git Repository Options: A) Github (Cloud with Automated backups from GitHub to CRAN Server): https://github.com B) Gitlab (Selfhosted on CRAN): https://about.gitlab.com C) Phabricator (Selfhosted on CRAN): https://www.phacility.com D) Microsoft Codeplex: https://www.codeplex.com E) Others: Unknown GOOGLE TRENDS: https://trends.google.com/trends/explore?date=all&q=Git,Svn,Github,Gitlab EXAMPLE Git Repository on Core Python: https://github.com/python PERSONAL OPINION / MOTIVATION: I think that moving efforts in th...

...ion as well, I find GitHub review is frustrating in comparison to phab, in particular the way comments are handled across updates, unless you stick to never rebase and only append commits and merges from master. This is unfortunately not compatible with the LLVM repo history right now. https://www.phacility.com offers hosting for Phabricator, could we look into this instead? -- Mehdi > . The original post on this thread indicated interest in not maintaining > Phabricator. How does that affect the availability of Phabricator? Does > this mean that the community is going to move to GitH...

...bug pull requests on the R-devel Git Repository. > > ? Git Repository Options: > A) Github (Cloud with Automated backups from GitHub to CRAN Server): > https://github.com > B) Gitlab (Selfhosted on CRAN): https://about.gitlab.com > C) Phabricator (Selfhosted on CRAN): https://www.phacility.com > D) Microsoft Codeplex: https://www.codeplex.com > E) Others: Unknown > > GOOGLE TRENDS: > https://trends.google.com/trends/explore?date=all&q=Git,Svn,Github,Gitlab > > EXAMPLE > Git Repository on Core Python: https://github.com/python > > PERSONAL OPINION...

...is frustrating in comparison to phab, in particular the way comments are handled across updates, unless you stick to never rebase and only append commits and merges from master. This is unfortunately not compatible with the LLVM repo history right now. >>>> >>>> https://www.phacility.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.phacility.com&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=FoGsCICjgE6UWLw9CIP41RDjHyairJfa_grtWPIUev0&s=v_EtlEr2Ks7GaS2wr9kUgFYgmGGsXiejr_aM_GeZh1U&e=> offers hosting for Phabricator, coul...

...; comparison to phab, in particular the way comments are handled across > updates, unless you stick to never rebase and only append commits and > merges from master. This is unfortunately not compatible with the LLVM repo > history right now. > >>> > >>> https://www.phacility.com offers hosting for Phabricator, could we > look into this instead? > >> > >> > >> Last time I checked, they basically said they didn't want us (no > customizations, which LLVM folks still wanted). > > > > > > Well, if this is a deal brea...

...gt;> comparison to phab, in particular the way comments are handled across >> updates, unless you stick to never rebase and only append commits and >> merges from master. This is unfortunately not compatible with the LLVM repo >> history right now. >> >> https://www.phacility.com offers hosting for Phabricator, could we look >> into this instead? >> > > Last time I checked, they basically said they didn't want us (no > customizations, which LLVM folks still wanted). > Well, if this is a deal breaker for us, then we can also exclude GitHub...

...gt;> comparison to phab, in particular the way comments are handled across >> updates, unless you stick to never rebase and only append commits and >> merges from master. This is unfortunately not compatible with the LLVM repo >> history right now. >> >> https://www.phacility.com offers hosting for Phabricator, could we look >> into this instead? >> >> -- >> Mehdi >> >> >> >>> . The original post on this thread indicated interest in not maintaining >>> Phabricator. How does that affect the availability of Ph...

...ents are handled across >>> updates, unless you stick to never rebase and only append commits and >>> merges from master. This is unfortunately not compatible with the LLVM repo >>> history right now. >>> >>>> >>> >>>> https://www.phacility.com offers hosting for Phabricator, could we >>> look into this instead? >>> >>>> >>> >>>> -- >>> >>>> Mehdi >>> >>>> >>> >>>> >>> >>>>> >>> >>...

...is frustrating in comparison to phab, in particular the way comments are handled across updates, unless you stick to never rebase and only append commits and merges from master. This is unfortunately not compatible with the LLVM repo history right now. >>>> >>>> https://www.phacility.com offers hosting for Phabricator, could we look into this instead? >>>> >>>> -- >>>> Mehdi >>>> >>>> >>>>> >>>>> . The original post on this thread indicated interest in not maintaining Phabricator. How d...

...ticular the way comments are handled across >> updates, unless you stick to never rebase and only append commits and >> merges from master. This is unfortunately not compatible with the LLVM repo >> history right now. >> >>>> >> >>>> https://www.phacility.com offers hosting for Phabricator, could we >> look into this instead? >> >>>> >> >>>> -- >> >>>> Mehdi >> >>>> >> >>>> >> >>>>> >> >>>>> . The original post...

Could we ever consider adding https://github.com/r4nt/phabricator/tree/llvm-production as a new read/only observe Diffusion repository in reviews.llvm.org? I'd be happy to do code reviews? MyDeveloperDay On Tue, Jul 28, 2020 at 8:46 PM MyDeveloper Day <mydeveloperday at gmail.com> wrote: > Awesome, thanks for sharing > > Here is a patch (based off yours) but this adds the

...oss updates, unless you stick to > never rebase and only append commits and merges from > master. This is unfortunately not compatible with the LLVM > repo history right now. > >>>> > >>>> https://www.phacility.com offers hosting for > Phabricator, could we look into this instead? > >>>> > >>>> -- > >>>> Mehdi > >>>> > >>>> > >>>&g...

Many git commits in the monorepo look like the following: [Tag0][Tag1] Title line Summary: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque mauris neque, porta nec tristique at, sagittis vel nisi. Fusce pharetra nunc et mauris consequat venenatis. Reviewers: username0, username1 Reviewed By: username0 Subscribers: username2, username3,

Just my 2 cents here: we are working on enabling this as a part of bugzilla migration as PRs and issues are very tied inside GitHub. Stay tuned for updates! On Fri, Jun 19, 2020 at 3:45 PM Manuel Klimek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > -Chris' outdated email, +Chris' correct email :) > > On Fri, Jun 19, 2020 at 2:01 PM Manuel Klimek <klimek at