1701686 results for "*"

  • fragmention << https://blogs.igalia.com/schenney/find-in-page-highlight-styling
    [KevinMarks] at 2025-12-03 00:58
  • [preview] [aimee-gm] #10 Require Base URL & handle parser errors
    Loqi at 2025-12-03 00:53
  • aciccarello WDYT of the previous PR that's been waiting there and did you try using/merging it before you wrote yours? https://github.com/microformats/microformats-parser-website-node/pull/10
    [tantek] at 2025-12-03 00:52
  • Though if so that feels like it should be `PR -> next -> main (which deploys)`. It reads to me like `PR -> main (which deploys) -> next
    gRegor at 2025-12-03 00:16
  • Ah gotcha, sort of a `dev` branch of pre-release
    gRegor at 2025-12-03 00:14
  • Looks like there was supposed to be some version updates in a PR from a few years ago that never got merged
    [aciccarello] at 2025-12-03 00:12
  • I think the point is that next is where all PRs go but merging to main is when a release should be triggered
    [aciccarello] at 2025-12-03 00:12
  • Version bumped
    [aciccarello] at 2025-12-03 00:12
  • I'm a bit confused on the readme. First line says "The base branch is next. All PRs should target this branch
    gRegor at 2025-12-03 00:09
  • " but then the bullets have "Merge release/x.y.z to main. This will trigger the deployment." followed by merging main into next
    gRegor at 2025-12-03 00:09
Sort by:

Filter results by:

Tag

Query took 0.09s.


Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23