duckdb / duckdb/extension-template
Unexpected Billing from GitHub Actions. Suggestion for Template Adjustment.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 290
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
I noticed something unexpected today: approximately USD 13 was "billed" to my GitHub Actions account.
While this amount falls within the free tier and doesn't result in any actual charges, it still came as a surprise.
Given that I'm still actively developing the extension and it's far from complete, I hadn’t anticipated any billing activity.
The main concern, however, is that others who clone this repository might encounter a similar situation.
Would it make sense to disable GitHub Actions by default in the template to avoid unexpected usage?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's GitHub Actions configuration and the template setup used when others clone it. Determine how Actions usage could be disabled by default without breaking extension development, then confirm that a new clone does not trigger unexpected workflow usage while documenting how users can enable it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100