Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clean up generated files #639

Closed
YunaBraska opened this issue Dec 23, 2022 · 3 comments · Fixed by #641 or #746
Closed

Clean up generated files #639

YunaBraska opened this issue Dec 23, 2022 · 3 comments · Fixed by #641 or #746
Assignees
@paambaati
Labels
enhancement New feature or request released

Comments

@YunaBraska
Copy link

Describe the bug
This github action adds files to the repositiry which should be deleted after run. I always checking code climate files as i am updating my project in my pipelines

Version of codeclimate-action you're using
v3.2.0

Example links

Expected behavior
No changes on the repository

Additional context
N/A
@YunaBraska YunaBraska added the bug Something isn't working label Dec 23, 2022
@paambaati paambaati added enhancement New feature or request and removed bug Something isn't working labels Dec 23, 2022
@paambaati
Copy link
Owner

Marking this as an enhancement/feature request rather than a bug, as this isn't a guarantee that the Action makes anyway.

I will be fixing this in a follow-up PR soon though.

paambaati added a commit that referenced this issue Dec 23, 2022
@paambaati
feat(core): cleanup downloaded artifacts
f331896 
Fixes #639
@paambaati paambaati mentioned this issue Dec 23, 2022
Merged
@YunaBraska
Copy link
Author

Thanks for fixing this. Maybe you could just use temp folders in the future.

github-actions bot pushed a commit that referenced this issue Apr 23, 2023
@paambaati
chore(release): 4.0.0
cdbb31e 
# [4.0.0](v3.1.0...v4.0.0) (2023-04-23)

### Bug Fixes

* **ci:** debug outputs ([11ed927](11ed927))
* **ci:** fix invalid YAML ([8f95f43](8f95f43))
* **ci:** fix the tag detection logic for new releases ([f787a56](f787a56))
* **ci:** rebuild and republish to use new branch and workflows ([0c99fb3](0c99fb3))
* **ci:** republish so latest changes get applied ([8f00eaa](8f00eaa))
* **ci:** republish so latest changes get applied ([fa71c1f](fa71c1f))
* **ci:** set up correct (?) condition to trigger publish ([3e9c9ce](3e9c9ce))
* **ci:** try once again to publish new version ([bcd27f6](bcd27f6))
* **ci:** use the un-broken latest version of the workflow ([0fe0643](0fe0643))
* **ci:** validate empty new release version ([2b9684a](2b9684a))
* **core:** support ARM 64-bit environments ([ea13673](ea13673))
* **core:** support ARM 64-bit environments ([99e22b3](99e22b3))

### Features

* **core:** cleanup downloaded artifacts ([f331896](f331896)), closes [#639](#639)
* **core:** support fork PRs. ([70a75ac](70a75ac)), closes [#627](#627)

### BREAKING CHANGES

* **ci:** semantic-release and its process is fundamentally broken when the repo moved from master to main for its main branch. This is an attempt to try to unfuck the git log/ref notes
@paambaati
Copy link
Owner

🎉 This issue has been resolved in version 4.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

This was referenced Apr 26, 2024
Merged
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paambaati paambaati

Labels
enhancement New feature or request released
Projects
None yet
Milestone
No milestone
2 participants
@paambaati @YunaBraska