browser extension | notes | kipras melnikovas

browser extension

words:	1 + 482 = 483
last update:

#public

Linked Mentions (3 in 2 pages)

January 24th, 2022 (2)

though, i intentionally don't put the [[host-specific adapters for git-stacked-rebase]] as the first priority here, because it feels like being able to integrate into the existing ecosystem, while creating some additional extras ([[browser extension]]) to make it easier to use [1], is the right approach
{{[[TODO]]}} a thought that's been circulating the past few days -- eventually, if/when we make the tool (both CLI & the underlying library) good, it might make sense to explore the possibilities of creating a [[browser extension]] for e.g. [[github]], that would allow it's users to view stacked diffs in the same PR (design of the tool checks out as well w/ this specific case)
- though, i haven't used [[(hidden) Qb76iqf_n]] myself and don't know how good it could look like -- would be really interesting to see beforehand.
- because we might not even need this at all, and perhaps the [[host-specific adapters for git-stacked-rebase]] would be completely enough to automate the manual parts so that it wouldn't matter as much of having multiple PRs vs one
  - though, i intentionally don't put the [[host-specific adapters for git-stacked-rebase]] as the first priority here, because it feels like being able to integrate into the existing ecosystem, while creating some additional extras ([[browser extension]]) to make it easier to use [1], is the right approach
  - [1] i think specifically the issue of having comments in separate PRs is important -- if you decide to split out a PR into multiple ones, then some comments will get lost, because we do not control in which PR they appear - we only control the PRs & the commits.
    - but, if we had the single PR + extension, we could now play w/ the comments, or perhaps wouldn't need to do much if anything at all, since you'd only have an extra partial branch / diff to cycle through the UI when reviewing - the comments/changes would remain in the same place.
- [[(hidden) Qb76iqf_n]] is out of maintenance, i can't even try out stacked diffs lol
  - searching "mercurial stacked diffs"
    - https://news.ycombinator.com/item?id=18137995
      - {{[[DONE]]}} #read [[(hidden) URRQcDCig]]'s [[(hidden) QNhvoR74k]]
        
        https://cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext
        
        very interesting stuff!
        
        so the whole thing is hosted and you pretty much don't use it locally. cool, but kinda meh!
        
        they have e.g. custom extensions for editors to be able to access & edit -- at least they didn't start creating their own editors & stuff - very surprising, but in a good way
        
        i prefer monorepos myself. ofc, haven't worked anywhere near close to such scale, but would be amazing if [[git]] had more of a first-hand support, incl. an eco-system around it... [[(hidden) 42siTzw1w]]
        
        https://pipedrive.slack.com/archives/C7R3EPWER/p1568022631016000
        
        https://github.com/microsoft/TypeScript/issues/33272
        
        (hidden) D8S_bYZuo #[[(hidden) 7c2C8PgIV]]
        
        hmmm. [[(hidden) URRQcDCig]] is using [[typescript]] extensively as well (kinda knew it already from e.g. [[(hidden) stBI9LNFL]])
        
        i then wonder how the #bs w/ [[pipeline operators]] is still going thru -- do they not see the issues / the optimal solution being different?
        
        (hidden) _XaekBjng

June 28th, 2022 (1)

(hidden) aQopx0HfW [[browser extension]] [[(hidden) YG4v50EAO]] is::