[UPSTREAM CHANGES] latest changes as of Mon Jul 27 2026 02:47:41 GMT+0000 (Coordinated Universal Time) - #348
Open
github-actions[bot] wants to merge 1733 commits into
Open
[UPSTREAM CHANGES] latest changes as of
Mon Jul 27 2026 02:47:41 GMT+0000 (Coordinated Universal Time)#348github-actions[bot] wants to merge 1733 commits into
github-actions[bot] wants to merge 1733 commits into
Conversation
Transparent logos for dark theme See merge request glitchtip/glitchtip-frontend!622
built-in subscription pricing and upgrade banner See merge request glitchtip/glitchtip-frontend!660
Changes to better format and style ios frames See merge request glitchtip/glitchtip-frontend!624
Default-type issues from pure log events (no exception) ingest with
Issue.title populated but Issue.metadata = {}. The detail component
derived its title purely from metadata, leaving the header blank even
though the title was present on the issue. Use issue.title as a
fallback across all branches, matching the issue list which already
reads issue.title directly.
Closes #358
- Split upgrade variant into approaching-limit vs. throttling messages
- Drop "up to {top} events/month" claim from upgrade body
- Soften get-started variant with "and beyond" qualifier
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
When usagePercent is null (under 80% threshold from parent), render a generic supportive message instead of nothing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Wraps long lines and uses trailing-> attribute style to match the prevailing Angular template style in the rest of the codebase. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fix: fall back to issue.title when metadata is empty Closes #358 See merge request glitchtip/glitchtip-frontend!673
fix: remove price is_public, meta data See merge request glitchtip/glitchtip-frontend!675
fix stuck spinner and stale subscription view on re-navigation See merge request glitchtip/glitchtip-frontend!677
feat(mfa): gate setup on verified email with explanatory banner See merge request glitchtip/glitchtip-frontend!676
… feat/tweak-support
feat(issues): show loading progress without blanking the list Closes #247 See merge request glitchtip/glitchtip-frontend!728
refactor: retire gt-to-do-item, add a Stepper guide page See merge request glitchtip/glitchtip-frontend!737
Introduce a shared gt-empty-state (centered icon, title, short message and one optional projected action) so every no-data state reads the same instead of each list rolling its own text. Spacing uses --gt-space with px fallbacks so it works before the token promotion lands. Adopt it in the three data tables that showed bare text in their no-data row: Uptime Monitors, Releases and Performance. Each reuses its feature's own nav icon. Document the component in the component preview.
Logs now shows two distinct states: a first-run "No logs yet" pointing at SDK setup, and a "No matching logs" state when a search or filter returns nothing. Project alerts uses the shared component too. Remove the now-dead .log-no-data and .no-alerts styles.
…cial logins Replace the one-line "empty" text in the API tokens and social logins cards with the shared component, and drop the now-dead .empty-state / .empty-auth styles.
The title now renders as a heading (default aria-level 3) so it appears in the heading outline and screen-reader users can navigate to it, matching how Atlassian and PatternFly expose headingLevel. Document the input in the preview.
A filtered no-results state should read the same everywhere, so match the issues no-results icon instead of the logs feature icon.
…arding Classify the issues zero-state into a single zeroStateKind (no-projects, no-access, onboarding, no-results) so the states are mutually exclusive and never stack. Render no-projects, no-access and no-results with the shared gt-empty-state; no-results gains a Clear filters action. Onboarding: fold the configuration reference and optional features behind an "Optional setup" expander, keep a short in-context config pointer, guard the settings link against a missing project slug, and drop a duplicated getting-started block. Remove the now-dead .not-on-team style.
Fix: change free plan pricing wording. See merge request glitchtip/glitchtip-frontend!742
A reusable wrapper that shows a top indeterminate progress bar while its projected list/table reloads, keeping the previous rows visible but dimmed and non-interactive (aria-busy) instead of blanking out. Owns the whole reloading treatment (positioning, bar, dim, transition) so every list can share one pattern. Pair it with keepPreviousValue() in the data source. Documented as a stable component in the design-system preview.
Replace the page's inline loading bar + is-reloading styles with the shared gt-loading-overlay so the issues list uses the same reloading treatment as every other list. No behaviour change.
Keep the previous rows during a reload (keepPreviousValue on the data and pagination) and show the shared top progress bar instead of blanking the table or spinning the pagination control.
Keep the previous rows during a reload and show the shared top progress bar instead of blanking the table on filter, sort or pagination changes.
Keep the previous rows during a reload and show the shared top progress bar on the monitor list and the monitor checks table, including the all-checks/incidents toggle.
Wrap the report list in gt-loading-overlay so a page change keeps the previous reports visible under the shared top progress bar, instead of swapping the list for a centered spinner and hiding the nav arrows.
Feat/tweak support See merge request glitchtip/glitchtip-frontend!744
feat(empty-state): add shared gt-empty-state and adopt in data tables See merge request glitchtip/glitchtip-frontend!745
feat(subscription): opt-in metered overage billing UI See merge request glitchtip/glitchtip-frontend!714
…ding # Conflicts: # projects/component-preview/src/app/registry.ts # src/app/performance/transaction-groups/transaction-groups.ts # src/app/releases/releases.ts # src/app/uptime/monitor-list/monitor-list.component.ts
The logs page cleared its rows on every filter change (resetAccumulation set the accumulated list to []), so a level, service, search or date change blanked the terminal and showed a 'Loading logs...' block. Bring it in line with the rest of the app: wrap the output in gt-loading-overlay so a reload shows the shared top progress bar over the previous rows, dimmed and non-interactive, instead of emptying the list. The accumulator now keeps the previous rows until the new page arrives and replaces them; only the cached hit count resets on a filter change so the header count still reflects the new query. Load-more (cursor) still appends and sits outside the overlay, so paging never dims the existing rows.
Running Prettier over the views wrapped in gt-loading-overlay: the wrapped table/output contents were left at their original indentation, so the whole region is shifted in by one level to match the new nesting. Also trims two over-long comments on the logs hit-count reset down to one line each.
feat: unify list reloading with a shared gt-loading-overlay component See merge request glitchtip/glitchtip-frontend!746
github-actions
Bot
requested review from
Nanyte25,
npecka,
pat-cremin,
robshelly and
sclarkso
as code owners
July 27, 2026 02:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is auto-generated by
actions/github-script.