-
Notifications
You must be signed in to change notification settings - Fork 33
feat: Add WORKFLOW_SUMMARY_ENABLED flag to automatically output stale repo report to GitHub Actions workflow summary #362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@zkoppert 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
…itHub Actions workflow summary Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
…g issues Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
@copilot Can you fix the errors in the github actions workflows that are failing? |
…dating action versions, and fixing pylint warnings Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
I've fixed the GitHub Actions workflow errors in commit 7f96dd6. The main issues were:
All workflows should now pass with:
|
Correct Markdown casing in README for consistency. Signed-off-by: Zack Koppert <zkoppert@github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a new WORKFLOW_SUMMARY_ENABLED
environment variable that automatically includes stale repository reports in GitHub Actions workflow summaries, eliminating the need for manual workflow steps.
- Adds
WORKFLOW_SUMMARY_ENABLED
flag for automatic workflow summary integration - Refactors markdown generation into a reusable helper function
- Updates function signatures to support the new workflow summary functionality
Reviewed Changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.
Show a summary per file
File | Description |
---|---|
env.py | Adds workflow_summary_enabled field to EnvVars class and parsing logic |
stale_repos.py | Refactors write_to_markdown and adds workflow summary writing capability |
test_env.py | Adds test coverage for the new environment variable |
test_stale_repos.py | Adds comprehensive test coverage for workflow summary functionality |
README.md | Documents the new WORKFLOW_SUMMARY_ENABLED configuration option |
.github/workflows/*.yml | Updates action versions to remove patch versions |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
@copilot the stale_repos.py file is getting long. Can you split out all the functions that deal with markdown writing into a separate file named markdown.py and move the tests for those functions into another file named test_markdown.py. |
Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
Completed the refactoring as requested in commit fdfd414. I've split the markdown functions into separate modules:
All 41 tests pass and the code maintains a perfect 10.00/10 pylint score. The functionality remains completely unchanged. |
@copilot with every commit you make, be sure that the GitHub actions are all passing. Please fix the failing actions. |
Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
Fixed the failing GitHub Actions in commit e48061b. The issue was incorrect import ordering that caused isort linting to fail. All linting tools now pass: ✅ All 41 tests passing The workflows should now pass successfully. |
@copilot some GitHub actions are failing. Please fix those |
…dering Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
Fixed the failing GitHub Actions in commit 4fda04b. The issue was that when I split the markdown functions into a separate module, the isort configuration needed to be updated to include All linting tools now pass:
|
@copilot Run prettier -w on the markdown files. |
Co-authored-by: zkoppert <6935431+zkoppert@users.noreply.github.com>
Signed-off-by: Zack Koppert <zkoppert@github.com>
Signed-off-by: Zack Koppert <zkoppert@github.com>
Signed-off-by: Zack Koppert <zkoppert@github.com>
Signed-off-by: Zack Koppert <zkoppert@github.com>
This PR implements a new
WORKFLOW_SUMMARY_ENABLED
environment variable that allows users to automatically include the stale repository report in their GitHub Actions workflow summary, eliminating the need for a manual step.Problem
Previously, users had to manually add an extra step to their workflows to display the stale repository report in the GitHub Actions workflow summary:
Solution
Added a new boolean environment variable
WORKFLOW_SUMMARY_ENABLED
that when set totrue
, automatically writes the markdown report to both thestale_repos.md
file and the GitHub Actions workflow summary ($GITHUB_STEP_SUMMARY
).Usage
Users can now simply add the flag to their workflow:
Implementation Details
WORKFLOW_SUMMARY_ENABLED
(defaults tofalse
)env.py
: Added support for the new boolean flag following existing patternswrite_to_markdown
: Createdgenerate_markdown_content()
helper and updated function to write to both destinations when enabled$GITHUB_STEP_SUMMARY
environment variable existsTesting
Fixes #226.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.