ci: exempt Server-Side Enhancement label from stale bot - #1841
Open
jacalata wants to merge 2 commits into
Open
Conversation
Issues blocked on server-side REST API work have no client-side activity to accumulate, so the stale bot would repeatedly flag them by default. Exempt the `server-side-gap` label (used to mark issues that need a server-side fix and cannot be resolved in TSC alone) so those items stay open until the underlying server work lands. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The repo already has a 'Server-Side Enhancement' label applied to issues blocked on server-side REST API work (e.g. #1716, #1658, #1537, #1508). Adding a parallel 'server-side-gap' label would have been redundant. Point the stale-bot exemption at the existing label. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jacalata
changed the title
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
1 participant
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.
@bcantoni thoughts? The other option is that we let these server-side bugs close and just let the docs list point to both open and closed bugs in the label.
Summary
Adds the existing
Server-Side Enhancementlabel to the stale-action'sexempt-issue-labelslist, so issues that are legitimately blocked on Tableau server REST API work stay open without needing manual rescue every 60 days.Without this exemption, every one of those issues would flap between "labeled stale" and "manually kept alive" indefinitely — but the user has no client-side activity they can add, because the fix isn't in this repo.
Companion to #1842 which adds a "Known server-side limitations" section to
docs/api-ref.mdand points at this label as the live tracker.Test plan
good first issue,Design Proposal,in-progress) preservedworkflow_dispatchrun of the stale action removes thestalelabel from any issue that also hasServer-Side Enhancement(e.g. Update_connection() returned 400033 Bad Request for on-premise solution #1716, Unabled to create Subscriptions with schedule as "On Extract Refresh" #1658, Flow image unavailable when using flows publish method #1537, Extract Refresh task with a Daily schedule don't work as expected #1508 currently in that state)🤖 Generated with Claude Code