[BUG] - Broken statistics workflow
See original GitHub issueThe statistics workflow, which is integrated in the community.yml
file, throws errors on forked repos (and sometimes on PRs). I believe this is due to the fork missing the FIREBASE_KEY
secret.
Is this workflow intended to run on everything? Or should it be migrated into its own .yml
file and set to run on specific events?
statistics:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- uses: EddieJaoudeCommunity/gh-action-community/src/statistics@main
with:
firebase-key: ${{ secrets.FIREBASE_KEY }}
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (11 by maintainers)
Top Results From Across the Web
How to Build the Perfect Jira Workflow for Bug Tracking - iDalko
The most effective bug tracking workflows will enable your team to identify, record and track bugs. And to access the issues from a...
Read more >Data Bugs & How to Fix Them | DAGsHub Blog
In this post, I'd like to share my personal story of a data bug, which is very indicative of the types of bugs...
Read more >A Pain-Free Workflow For Issue Reporting And Resolution
1. Assign Someone To Triage # · Monitoring for reported issues. · Adding the bugs to the queue. · Ushering them through the...
Read more >How to Write Good Bug Reports And Gather Quality Metrics Data
Learn what data you need to include in a good bug report. ... Moreover, we will look into bug statuses what an upgraded...
Read more >8 Bug Tracking Tools (and Workflows): How Top Technical ...
The simplest way to track bugs is with a basic excel sheet. List the bugs, info about them, and work through them when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Since, that workflow was removed, I think it’s safe to close this issue.
I think this is still broken ._. Stalebot, this is still needed 🙃