Skip to content

Conversation

@xgboosted
Copy link
Contributor

@xgboosted xgboosted commented May 14, 2025

Summary

This PR introduces built-in retry logic for the runner creation step, addressing issue #8.

I have tested it by releasing the Action in the GH Marketplace, it works fine.

Features

  • New Inputs

    • create_retries: Number of retry attempts for runner creation (default: 1)
    • create_retry_delay: Delay in seconds between attempts (default: 10)
  • Enhancements

    • Automatic retries for runner creation on transient Hetzner or network errors.
    • Configurable number of attempts and delay between attempts.
    • Clear logging for each attempt and final failure.
    • Backward compatible: defaults to single attempt if new inputs are not set.
  • Documentation

    • Updated README.md with usage instructions and input documentation.
    • Example workflow snippet included.
  • Refactoring

    • Refactored action.sh for improved readability and maintainability.
    • Restored proper Unix line endings and formatting.
    • Grouped input parsing and validation for clarity.

xgboosted added 4 commits May 14, 2025 21:06
- Introduce `create_retries` and `create_retry_delay` inputs to control retry attempts and delay for runner creation failures
- Update README with new inputs and retry logic explanation
- Refactor action.sh for improved readability and to support retry mechanism
Clarify the action name by shortening it to 'Self-Hosted GitHub Actions Runner on Hetzner' for consistency and simplicity.
Clarify that the action is for Hetzner Cloud by updating the name field in action.yml. This helps distinguish it from other Hetzner services and improves discoverability.
Remove invisible BOM character from the shebang line to ensure proper script execution in Unix environments.
@Cyclenerd
Copy link
Owner

Thank you for your pull request. Please take a close look at CONTRIBUTING.md and update your work. You have deleted quite a lot and made unnecessary changes. We indent with tabs in Shell scripts. Do not delete comments. First removing the Word Cloud and then adding it again is also unnecessary.

@xgboosted
Copy link
Contributor Author

Thanks for pointing out the coding style issue. I will redo this with a new PR.

@xgboosted xgboosted closed this May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants