Update documentation for [skip actions] approach
- Update GITEA-ACTIONS-SETUP.md to document [skip actions] flag usage - Explain infinite loop prevention using standard Gitea Actions approach - Remove references to conditional workflow execution based on commit message detection - Document simplified git configuration using inline -c flags - Provide clear explanation of how [skip actions] prevents recursive workflow execution
This commit is contained in:
@@ -65,6 +65,12 @@ on:
|
|||||||
branches: [ main ]
|
branches: [ main ]
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Infinite Loop Prevention
|
||||||
|
The workflow uses the `[skip actions]` flag in commit messages to prevent infinite loops:
|
||||||
|
- When files are moved, the commit message includes `[skip actions]`
|
||||||
|
- This prevents the workflow from triggering again on its own commits
|
||||||
|
- Standard Gitea Actions approach for preventing recursive execution
|
||||||
|
|
||||||
### Authentication Method
|
### Authentication Method
|
||||||
The workflow uses token-based authentication and dynamically detects the repository URL:
|
The workflow uses token-based authentication and dynamically detects the repository URL:
|
||||||
```yaml
|
```yaml
|
||||||
|
|||||||
Reference in New Issue
Block a user