Atmos Pro Logo

Atmos Pro

ProductPricingDocsBlogChangelog
Create Workspace
← Back to Changelog
Enhancement

Repairs Flags Repositories With GitHub Issues Disabled

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

|October 7, 2026

Older

Status Comments Group Stacks by the Workflow That Ran

Newer

Dispatched Workflows Can Now Receive the Pull Request Number

Erik Osterman

Erik Osterman

CEO & Founder of Cloud Posse

Erik is the founder of Cloud Posse and creator of Atmos. With over a decade of experience helping teams adopt Terraform at scale, he is passionate about open-source infrastructure tooling and developer experience.

Book a Meeting
Atmos Pro Logo

Atmos Pro

The fastest way to deploy your apps on AWS with Terraform and GitHub Actions.

GitHubTwitterLinkedInYouTubeSlack

For Developers

  • Quick Start
  • Example Workflows
  • Atmos Documentation
  • Register for Office Hours
  • Join the Slack Community

Enterprise

  • Trust Center
  • Procurement
  • Pricing
  • Contact Sales

Company

  • Support
  • About Cloud Posse
  • Security
  • Blog
  • Media Kit
  • Try our Newsletter

Legal

  • SaaS Agreement
  • Terms of Use
  • Privacy Policy
  • Disclaimer
  • Cookie Policy

© 2026 Cloud Posse, LLC. All rights reserved.

Checking status...
Release status comments are posted as GitHub issue comments. If GitHub Issues are disabled on a repository, Atmos Pro cannot post them, and until now nothing told you why the comment was missing.
The Repairs page now lists every repository where Issues are disabled and at least one of your Atmos workflows is configured for the release event. Each row links straight to that repository's settings on GitHub, where you can turn Issues back on. The warning clears on its own once Issues are enabled again.

When It Updates

GitHub does not notify Atmos Pro when this setting changes, so the check relies on the repository metadata refresh that already runs every few hours. After you change the setting, allow up to about a day for the Repairs page to catch up.
Repositories are checked for the first time as that refresh reaches them, so a repository with Issues already disabled can take a little while to appear after this change ships. A repository that has never had a workflow run has no stored workflow configuration yet, so it is not flagged until its first run.