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.

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

Add scripts for automated development contribution #1040

Merged

Conversation

quantumryuu
Copy link
Contributor

@quantumryuu quantumryuu commented Dec 27, 2024

🛠️ Note:
We are meticulous about merging code into the main branch, so please understand that pull requests not meeting the project's standards may be rejected. It's never personal!
🎮 Note for game-related scripts: These have a lower likelihood of being merged.


✍️ Description

Please see everything inside the dev-scripts folder!
I have a readme file with the breakdown and steps needed for the scripts.
Essentially what these scripts do is to setup a branch for creating a new helper script and automate a couple of things that may be forgotten like changing the build.func, install.func etc to point to the new branch instead of the official repo!
@michelroegl-brunner there you go mate, they're rough around the edge since they were developed for personal use but the workflow works! Although change_lxc.sh and cleanup_lxc.sh need a bit of more testing, new_lxc.sh seems to work for my needs pretty good (tested with 3-4 new helper scripts that I created a PR for them!)


Please remove unneeded lines!


🛠️ Type of Change

Please check the relevant options:

  • Bug fix (non-breaking change that resolves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change unexpectedly)
  • New script (a fully functional and thoroughly tested script or set of scripts)

✅ Prerequisites

The following steps must be completed for the pull request to be considered:

  • Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.)
  • Testing performed (I have thoroughly tested my changes and verified expected functionality.)
  • Documentation updated (I have updated any relevant documentation)

📋 Additional Information (optional)

@quantumryuu quantumryuu requested a review from a team as a code owner December 27, 2024 15:41
@github-actions github-actions bot added the maintenance Code maintenance or general upkeep of the project label Dec 27, 2024
@michelroegl-brunner michelroegl-brunner changed the base branch from main to contributor_guide December 27, 2024 15:42
@michelroegl-brunner
Copy link
Member

Thank you, ill have a look!

@quantumryuu
Copy link
Contributor Author

Thank you, ill have a look!

Not really used to writing bash scripts, I'm more of a PowerShell guy, so excuse my poor bash scripting skills 😁

@michelroegl-brunner michelroegl-brunner changed the base branch from contributor_guide to new_script_testing December 27, 2024 17:39
@michelroegl-brunner
Copy link
Member

All good. I merhe it in a sepereate branch for testing.

@michelroegl-brunner michelroegl-brunner merged commit 8c23f87 into community-scripts:new_script_testing Dec 27, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Code maintenance or general upkeep of the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants