alice.pds.demo.boltless.dev
Commits
Signed-off-by: oppiliappan <me@oppi.li>
Signed-off-by: oppiliappan <me@oppi.li>
- login bg fixed
- profile edit button icon-size fixed
- star button fill color fixed
Signed-off-by: oppiliappan <me@oppi.li>
Signed-off-by: dawn <dawn@tangled.org>
Signed-off-by: dawn <dawn@tangled.org>
Fixes #364
Allows users to manually change theme, useful for cases like
LibreWolf where it defaults to light-mode irrespective of system
settings (with resistFingerprinting enabled).
Stores theme as 'light', 'dark', or 'auto' in the database, and
dynamically adds/removes the 'dark' class from the HTML.
Signed-off-by: TheBananaPancake <did:plc:3ywraszv5eqhnlvzumwju5fa>
Signed-off-by: oppiliappan <me@oppi.li>
Signed-off-by: oppiliappan <me@oppi.li>
Signed-off-by: oppiliappan <me@oppi.li>
Signed-off-by: oppiliappan <me@oppi.li>
Signed-off-by: Seongmin Lee <git@boltless.me>
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
Similar to follow records from previous commit, deduplicate stars.
Define a `deduped_stars` view to query deduplicated stars. Oldest star
wins so refreshing stars won't put repository to trending list.
Signed-off-by: Seongmin Lee <git@boltless.me>
From model layer, we expect follows to be unique per (did, subject). But
from PDS, there is no such constraint. So hide the rkey from model while
keeping duplicated records in DB.
We keep duplicated records in DB to delete them all at once on unfollow
Signed-off-by: Seongmin Lee <git@boltless.me>
passing untyped dict so `.HxSwapOob` will resolve to nil, not panic.
Signed-off-by: Seongmin Lee <git@boltless.me>
add `BaseParams` to `LoginParams`. We won't set it, but it will make
template to render without failing.
Signed-off-by: Seongmin Lee <git@boltless.me>
It's just style change which can be done by CSS.
Signed-off-by: Seongmin Lee <git@boltless.me>
Signed-off-by: Seongmin Lee <git@boltless.me>
Signed-off-by: Seongmin Lee <git@boltless.me>
Signed-off-by: Seongmin Lee <git@boltless.me>
Signed-off-by: Seongmin Lee <git@boltless.me>
Signed-off-by: oppiliappan <me@oppi.li>
was a minor regression from manual-runs
Signed-off-by: oppiliappan <me@oppi.li>
if a user skips onboarding at step 0, empty profile records were not
created.
Signed-off-by: oppiliappan <me@oppi.li>
both pages now have an "advanced" section for users to configure
spindles, the default selection is "No Spindle"
Signed-off-by: oppiliappan <me@oppi.li>
Signed-off-by: dawn <dawn@tangled.org>
Signed-off-by: Anirudh Oppiliappan <x@icyphox.sh>
Signed-off-by: Anirudh Oppiliappan <x@icyphox.sh>
Signed-off-by: dawn <dawn@tangled.org>
This adds five new webhook event types alongside the existing `push` and
`repository:renamed` events:
- `pull_request:created`
- `pull_request:resubmitted`
- `pull_request:merged`
- `pull_request:closed`
- `pull_request:reopened`
Each event carries a payload with an `action` field, pull request metadata (number, title, state,
target branch, source branch/repo/sha), the repository object, and the sender. The patch itself is
not embedded; payloads include a `patch_url` pointing at the existing raw round-patch route instead.
Merge, close, and reopen reuse the existing `NewPullState` notifier call sites. `Resubmission`
previously emitted no notifier event at all, so this adds a `ResubmitPull` method to the `Notifier`
interface, fired from both the regular and stacked resubmit paths (stacked resubmits also now fire
`NewPull` for pulls newly added to a stack). Stack-pull abandonment intentionally emits no event.
The webhook notifier now takes the appview base URL so pull request `html_url`/`patch_url` point at the
appview, where pull routes live (`repository.html_url` keeps pointing at the knot, unchanged).
Refs #97, #94.
Fixes [#672](https://tangled.org/tangled.org/core/issues/672)
Signed-off-by: dawn <dawn@tangled.org>
Set the `color-scheme` property such that css functions like
`light-dark` work correctly, and any un-customised native elements use
the correct theme
Fixes #364
Allows users to manually change theme, useful for cases like
LibreWolf where it defaults to light-mode irrespective of system
settings (with resistFingerprinting enabled).
Stores theme as 'light', 'dark', or 'auto' in the database, and
dynamically adds/removes the 'dark' class from the HTML.
Signed-off-by: TheBananaPancake <did:plc:3ywraszv5eqhnlvzumwju5fa>
This adds five new webhook event types alongside the existing `push` and
`repository:renamed` events:
- `pull_request:created`
- `pull_request:resubmitted`
- `pull_request:merged`
- `pull_request:closed`
- `pull_request:reopened`
Each event carries a payload with an `action` field, pull request metadata (number, title, state,
target branch, source branch/repo/sha), the repository object, and the sender. The patch itself is
not embedded; payloads include a `patch_url` pointing at the existing raw round-patch route instead.
Merge, close, and reopen reuse the existing `NewPullState` notifier call sites. `Resubmission`
previously emitted no notifier event at all, so this adds a `ResubmitPull` method to the `Notifier`
interface, fired from both the regular and stacked resubmit paths (stacked resubmits also now fire
`NewPull` for pulls newly added to a stack). Stack-pull abandonment intentionally emits no event.
The webhook notifier now takes the appview base URL so pull request `html_url`/`patch_url` point at the
appview, where pull routes live (`repository.html_url` keeps pointing at the knot, unchanged).
Refs #97, #94.