The new GitHub Issues – October 18th update

🧹 Keep your project tidy with auto-archive

As long-lived projects accumulate items over time, many users set aside time to archive old items to keep their projects focused on what matters most. Today we are introducing the public beta of a new workflow to archive items automatically so that you can get back to the things that matter!

Configure which items you’d like to archive by heading to the Workflow page, selecting Auto-archive items, and updating the filter. We support is, reason, and last-updated, and you can verify archived items by copying the filter query into a table view.

Set it up today to spend less time on pruning projects and let us know what you think in Discussions!

⚙️ Configure board column visibility

In addition to auto-hiding board columns with filters to customize your view, you can now hide a column directly from the column menu to populate the filter bar and configure which board columns are visible.

This can also be configured through the + menu, so you can now easily toggle which columns are shown or hidden on the view in addition to adding a new column.

✨ Bug fixes & improvements

Other changes include:

  • Adding hovercard functionality for links in the side panel
  • Fixed a bug that didn’t allow for assignees to be copy/pasted into a field for draft issues

See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the docs.

Introducing fine-grained personal access tokens

Today we're enabling fine-grained personal access tokens (PATs) in Public Beta for all user accounts on GitHub.com. This new type of token gives developers and resource owners more control and visibility around token access. Learn more about this new token type in today's blog post.

These new tokens offer many more permissions to choose from, must be scoped to a specific organization or account, and must expire. Organization owners will also find new tools to manage tokens that can access their organization, and can require approval of those tokens before they may be used.

PATsv2-light2

You can try out the new token creation flow, and provide feedback in our community discussion.

For more information, see "Creating a fine-grained personal access token".

See more

Secret scanning now runs a historical scan to detect newly added secret types

GitHub will regularly run a historical scan to detect newly added secret types on repositories with GitHub Advanced Security and secret scanning enabled.

Previously, customers could manually trigger a historical scan to detect new secret types by re-enabling secret scanning, e.g. clicking "Enable all" at the organization level. Now, historical scans are automatic; customers can expect an email of any new detections in their repositories, just like they would when first enabling secret scanning today.

See more
View all changes