Meta tags:
description=Marks issues and pull requests that have not had recent interaction - GitHub - actions/stale: Marks issues and pull requests that have not had recent interaction;

Headings (most frequently used words):

issue, pr, exempt, stale, labels, close, all, of, days, before, milestones, assignees, only, when, options, launching, message, label, remove, github, any, updated, ignore, updates, in, use, footer, license, list, code, desktop, to, unstale, actions, name, already, issues, and, prs, latest, commit, git, stats, files, readme, md, recommended, permissions, about, releases, 35, packages, used, by, 86, 8k, contributors, 65, languages, input, output, detailed, usage, debugging, contributing, resources, conduct, security, policy, stars, watchers, forks, navigation, sign, required, xcode, visual, studio, repo, token, reason, operations, per, run, add, debug, ascending, start, date, delete, branch, draft, enable, statistics, include, assigned, this, action, with, your, project,

Text of the page (most frequently used words):
the (239), stale (220), #issues (117), exempt (90), issue (87), only (81), pull (72), label (69), #requests (67), labels (67), days (67), and (62), all (59), default (59), this (56), close (56), for (55), value (54), will (51), before (50), you (48), prs (48), milestones (48), with (47), github (44), unset (41), assignees (38), override (38), when (38), that (37), message (37), can (34), workflow (28), remove (28), not (27), options (27), automatically (27), actions (24), number (23), any (23), comment (23), add (23), these (22), action (21), from (21), closed (21), but (21), updates (21), ignore (20), run (19), list (19), your (18), option (18), write (18), false (17), operations (16), true (16), latest (15), update (15), required (15), updated (15), 2022 (14), logs (14), are (14), set (14), name (14), date (14), permission (14), one (14), process (14), contain (14), cron (13), activity (13), marked (13), based (13), api (12), code (12), uses (12), branch (12), 2021 (12), because (11), repository (11), steps (11), ubuntu (11), runs (11), jobs (11), schedule (11), use (11), has (11), added (11), idle (11), per (10), allow (10), debug (9), open (9), new (9), limit (9), oct (8), more (8), statistics (8), start (8), been (8), assignee (8), useful (8), field (8), empty (8), string (8), alter (8), comma (8), delete (8), wish (8), unstale (8), token (8), staled (8), json (8), enable (7), after (7), mark (7), does (7), milestone (7), branches (7), closing (7), feat (7), about (6), security (6), used (6), could (6), very (6), 2020 (6), configure (6), updated_at (6), draft (6), separated (6), reason (6), feb (6), aug (6), daysbeforestale (6), float (6), time (5), license (5), marks (5), have (5), work (5), contributing (5), which (5), configuration (5), output (5), avoid (5), request (5), calls (5), removed (5), skip (5), marking (5), permissions (5), 291 (5), fix (5), 841 (5), commit (5), nothing (5), desktop (5), sign (5), tags (5), jump (5), packages (4), 269 (4), readme (4), had (4), helpful (4), increase (4), passing (4), help (4), rate (4), end (4), must (4), instead (4), needs (4), awaiting (4), was (4), provided (4), assigned (4), fetch (4), ascending (4), made (4), project (4), comments (4), repo (4), not_planned (4), exempted (4), apply (4), view (4), jun (4), create (4), try (4), again (4), launching (4), download (4), forks (3), stars (3), 847 (3), recent (3), interaction (3), please (3), change (3), job (3), never (3), dry (3), also (3), see (3), there (3), many (3), debugging (3), marco (3), specific (3), case (3), check (3), created (3), stalled (3), timeouts (3), yml (3), include (3), restart (3), display (3), consume (3), order (3), content (3), commented (3), like (3), manually (3), closes (3), defined (3), two (3), last (3), package (3), specified (3), input (3), tsconfig (3), changelog (3), 2019 (3), release (3), jan (3), licensed (3), licenses (3), load (3), git (3), happens (3), codespaces (3), web (3), discussions (3), signed (2), another (2), tab (2), window (2), refresh (2), session (2), reload (2), perform (2), blog (2), pricing (2), docs (2), footer (2), navigation (2), 100 (2), contributors (2), releases (2), policy (2), conduct (2), mit (2), resources (2), read (2), file (2), frequency (2), single (2), enabled (2), reach (2), able (2), 1000 (2), argument (2), once (2), secret (2), actions_step_debug (2), polo (2), present (2), iso (2), 8601 (2), rfc (2), 2822 (2), approval (2), progress (2), different (2), none (2), usage (2), purpose (2), them (2), counter (2), prefer (2), created_at (2), get (2), need (2), priority (2), over (2), contents (2), following (2), existing (2), old (2), want (2), warning (2), results (2), delimited (2), receives (2), higher (2), since (2), batch (2), plan (2), sure (2), reached (2), should (2), etc (2), fast (2), within (2), using (2), answered (2), rebase (2), longer (2), nor (2), locked (2), speedup (2), values (2), being (2), too (2), long (2), sending (2), negative (2), older (2), than (2), adding (2), creation (2), pat (2), under (2), detailed (2), description (2), they (2), become (2), checked (2), while (2), find (2), information (2), recommended (2), inactivity (2), core (2), 465 (2), coloured (2), sep (2), local (2), nov (2), 138 (2), verify (2), prod (2), dist (2), 65b52af (2), codespace (2), xcode (2), cli (2), https (2), tag (2), already (2), may (2), refname (2), show (2), belong (2), fork (2), outside (2), insights (2), projects (2), notifications (2), star (2), source (2), manage (2), out, training, contact, status, privacy, terms, inc, typescript, languages, 767, published, watching, watchers, welcome, contributions, starting, often, usually, though, maximum, example, handle, almost, deep, dive, into, mode, taken, log, visible, were, processed, quick, understanding, whole, opt, requires, info, demo, bugfix, improvement, future, alpha, beta, 18t00, 00z, 18th, april, feedback, answers, basic, comprehensive, define, considering, most, cases, necessary, occurs, nonetheless, don, care, stick, matter, comparing, collects, summary, what, happened, during, currently, operation, know, white, next, related, formatted, standard, particularly, processing, focus, descending, happen, safely, each, unique, call, drastically, much, fewer, actor, business, right, good, enough, look, telling, choose, might, unprocessed, aims, reaching, performs, some, short, period, numerous, quantity, block, hour, other, same, user, helps, stay, limits, context, wip, question, bug, specify, valid, completed, due, calculate, fine, tune, missing, notify, still, means, however, behaviour, matters, disable, personal, access, allows, authenticate, hood, reset, max, authentication, every, optional, corresponding, execution, addition, require, achieved, restricted, occur, timer, warns, then, amount, spec, app, lock, jest, config, 807, make, 829, initial, import, owners, tracking, codeowners, chore, provide, way, less, gru, versionrc, prettierrc, prettierignore, 199, spaces, inside, gitignore, gitattributes, eslintrc, apr, cleanup, eslintignore, src, reflect, __tests__, vscode, npm, jul, 761, build, deps, bump, setup, node, type, failed, permalink, files, commits, 328, stats, irega, problem, preparing, ready, visual, studio, zip, our, official, learn, checkout, svn, url, clone, cancel, exists, commands, accept, both, names, creating, cause, unexpected, behavior, switch, main, marketplace, public, organization, suggested, collections, trending, topics, repositories, community, articles, fund, developers, sponsors, customer, stories, studies, devsecops, devops, automation, solution, education, startups, teams, enterprise, solutions, skills, documentation, features, explore, collaborate, track, changes, review, better, copilot, instant, dev, environments, vulnerabilities, host, automate, product, toggle, wayback, machine, http, archive, org, 20221206072102, com, timestamps, capture, fail, success, 2023, dec, 2026, 645, captures,

Text of the page (random words):
as stale default value stale required permission pull requests write close pr label the label that will be added to the pull requests when closed automatically it will be automatically removed if the pull requests are no longer closed nor locked default value unset required permission pull requests write exempt issue labels the label s that can exempt to automatically mark as stale the issues it can be a comma separated list of labels e g question bug if unset or an empty string this option will not alter the stale workflow default value unset exempt pr labels the label s that can exempt to automatically mark as stale the pull requests it can be a comma separated list of labels e g need help wip if unset or an empty string this option will not alter the stale workflow default value unset only labels an allow list of label s to only process the issues or the pull requests that contain all these label s it can be a comma separated list of labels e g answered needs rebase if unset or an empty string this option will not alter the stale workflow if you wish to only check that the issues or the pull requests contain one of these label s use instead any of labels default value unset only issue labels override only labels but only to process the issues that contain all these label s default value unset only pr labels override only labels but only to process the pull requests that contain all these label s default value unset any of labels an allow list of label s to only process the issues or the pull requests that contain one of these label s it can be a comma separated list of labels e g answered needs rebase if unset or an empty string this option will not alter the stale workflow if you wish to only check that the issues or the pull requests contain all these label s use instead only labels default value unset any of issue labels override any of labels but only to process the issues that contain one of these label s default value unset any of pr labels override any of labels but only to process the pull requests that contain one of these label s default value unset operations per run context this action performs some api calls to github to fetch or close issues and pull requests set or update labels add comments delete branches etc these operations are made in a very short period of time because the action is very fast to run and can be numerous based on your project action configuration and the quantity of issues and pull requests within it github has a rate limit and if reached will block these api calls for one hour or api calls from other actions using the same user a k a the github token from the repo token option this option helps you to stay within the github rate limits as you can use this option to limit the number of operations for a single run purpose this option aims to limit the number of operations made with the github api to avoid reaching the rate limit based on your project your github business plan and the date of the cron job you set for this action you can increase this limit to a higher number if you are not sure which is the right value for you or if the default value is good enough you could enable the logs and look at the end of the stale action if you reached the limit you will see a warning message in the logs telling you that you should increase the number of operations if you choose not to increase the limit you might end up with unprocessed issues or pull requests after a stale action run when debugging you can set it to a much higher number like 1000 since there will be fewer operations made with the github api only the actor and the batch of issues 100 per batch will consume the operations default value 30 remove stale when updated automatically remove the stale label when the issues or the pull requests are updated based on github issue field updated_at or commented default value true required permission issues write and pull requests write remove issue stale when updated override remove stale when updated but only to automatically remove the stale label when the issues are updated based on github issue field updated_at or commented default value unset required permission issues write remove pr stale when updated override remove stale when updated but only to automatically remove the stale label when the pull requests are updated based on github issue field updated_at or commented default value unset labels to add when unstale a comma delimited list of labels to add when a stale issue or pull request receives activity and has the stale issue label or stale pr label removed from it default value unset labels to remove when unstale a comma delimited list of labels to remove when a stale issue or pull request receives activity and has the stale issue label or stale pr label removed from it warning each label results in a unique api call which can drastically consume the limit of operations per run default value unset required permission pull requests write debug only run the stale workflow as dry run no github api calls that can alter your issues and pull requests will happen useful to debug or when you want to configure the stale workflow safely default value false ascending change the order used to fetch the issues and pull requests from github true is for ascending false is for descending it can be useful if your repository is processing so many issues and pull requests that you reach the operations per run limit based on the order you could prefer to focus on the new content or on the old content of your repository default value false start date the start date is used to ignore the issues and pull requests created before the start date particularly useful when you wish to add this stale workflow on an existing repository and only wish to stale the new issues and pull requests if set the date must be formatted following the iso 8601 or rfc 2822 standard default value unset delete branch if set to true the stale workflow will automatically delete the github branches related to the pull requests automatically closed by the stale workflow default value false required permission pull requests write and contents write exempt milestones a white list of milestone s to only process the issues or the pull requests that does not contain one of these milestone s it can be a comma separated list of milestones e g v1 next if unset or an empty string this option will not alter the stale workflow default value unset exempt issue milestones override exempt milestones but only to process the issues that does not contain one of these milestone s default value unset exempt pr milestones override exempt milestones but only to process the pull requests that does not contain one of these milestone s default value unset exempt all milestones if set to true the issues or the pull requests with a milestone will not be marked as stale automatically priority over exempt milestones default value false exempt all issue milestones override exempt all milestones but only to exempt the issues with a milestone to be marked as stale automatically default value unset exempt all pr milestones override exempt all milestones but only to exempt the pull requests with a milestone to be marked as stale automatically default value unset exempt assignees an allow list of assignee s to only process the issues or the pull requests that does not contain one of these assignee s it can be a comma separated list of assignees e g marco polo if unset or an empty string this option will not alter the stale workflow default value unset exempt issue assignees override exempt assignees but only to process the issues that does not contain one of these assignee s default value unset exempt pr assignees override exempt assignees but only to process the pull requests that does not contain one of these assignee s default value unset exempt all assignees if set to true the issues or the pull requests with an assignee will not be marked as stale automatically priority over exempt assignees default value false exempt all issue assignees override exempt all assignees but only to exempt the issues with an assignee to be marked as stale automatically default value unset exempt all pr assignees override exempt all assignees but only to exempt the pull requests with an assignee to be marked as stale automatically default value unset exempt draft pr if set to true the pull requests currently in draft will not be marked as stale automatically ️ this option consume one operation per pull request to process because we need to fetch the pull request with the github api to know if it s a draft one or not default value false required permission pull requests read enable statistics collects and display statistics at the end of the stale workflow logs to get a summary of what happened during the run this option is only useful if the debug output secret actions_step_debug is set to true in your repository to display the logs default value true ignore updates the option days before stale will define the number of days before considering the issues or the pull requests as stale in most cases the purpose of this action is to only stale when necessary so if any update occurs or if a comment is added to them the counter will restart nonetheless if you don t care about this and you prefer to stick to this number of days no matter the update you can enable this option instead of comparing the number of days based on the github issue field updated_at it will be based on the github issue field created_at default value false ignore issue updates useful to override ignore updates but only to ignore the updates for the issues default value unset ignore pr updates useful to override ignore updates but only to ignore the updates for the pull requests default value unset include only assigned if set to true only the issues or the pull requests with an assignee will be marked as stale automatically default value false usage see also action yml for a comprehensive list of all the options basic name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with stale issue message message to comment on stale issues if none provided will not mark issues stale stale pr message message to comment on stale prs if none provided will not mark prs stale configure stale timeouts name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with stale issue message this issue is stale because it has been open 30 days with no activity remove stale label or comment or this will be closed in 5 days days before stale 30 days before close 5 configure different stale timeouts but never close a pr name close stale issues and pr on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with stale issue message this issue is stale because it has been open 30 days with no activity remove stale label or comment or this will be closed in 5 days stale pr message this pr is stale because it has been open 45 days with no activity remove stale label or comment or this will be closed in 10 days close issue message this issue was closed because it has been stalled for 5 days with no activity days before stale 30 days before close 5 days before pr close 1 configure different stale timeouts name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with stale issue message this issue is stale because it has been open 30 days with no activity remove stale label or comment or this will be closed in 5 days stale pr message this pr is stale because it has been open 45 days with no activity remove stale label or comment or this will be closed in 10 days close issue message this issue was closed because it has been stalled for 5 days with no activity close pr message this pr was closed because it has been stalled for 10 days with no activity days before issue stale 30 days before pr stale 45 days before issue close 5 days before pr close 10 configure labels name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with stale issue message stale issue message stale pr message stale pull request message stale issue label no issue activity exempt issue labels awaiting approval work in progress stale pr label no pr activity exempt pr labels awaiting approval work in progress only labels awaiting feedback awaiting answers configure the stale action to only stale issue pr created after the 18th april 2020 name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with start date 2020 04 18t00 00 00z iso 8601 or rfc 2822 avoid stale for specific milestones name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with exempt issue milestones future alpha beta exempt pr milestones bugfix improvement avoid stale for all pr with milestones name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with exempt all pr milestones true check stale for specific labels name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with any of labels needs more info needs demo you can opt for only labels instead if your use case requires all labels to be present in the issue pr avoid stale for specific assignees name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with exempt issue assignees marco polo exempt pr assignees marco avoid stale for all pr with assignees name close stale issues and prs on schedule cron 30 1 jobs stale runs on ubuntu latest steps uses actions stale v6 with exempt all pr assignees true debugging logs to see the debug output from this action you must set the secret actions_step_debug to true in your repository there are many logs so this can be very helpful statistics if the logs are enabled you can also enable the statistics log which will be visible at the end of the logs once all issues were processed this is very helpful to have a quick understanding of the whole stale workflow set enable statistics to true in your workflow configuration file dry run you can run this action in debug only mode no actions will be taken on your issues and pull requests by passing debug only to true as an argument to the action more operations you can increase the maximum number of operations per run by passing operations per run to 1000 for example which will help you to handle more operations in a single stale workflow run if the debug only option is enabled this is very helpful because the workflow will almost never reach the github api rate and you will be able to deep dive into the logs job frequency you could change the cron job frequency in the stale workflow to run the stale workflow more often ...