set --work-path config parameter #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fixes errors like fatal: [gitea]: FAILED! => {"msg": "The conditional check 'gitea_secret_key | length == 0' failed. The error was: Unexpected templating type error occurred on ({% if gitea_secret_key | length == 0 %} True {% else %} False {% endif %}): object of type 'AnsibleVaultEncryptedUnicode' has no len()
when using an encrypted string in vault for secrets
gitea secrets aren't necessarily strings
delete gh-action cron entry
gitea 1.15.4 released
user gitea is now part of gitea group
gitea v1.15.5 available
v1.15.6 released
v1.16.7 is available
minor but important typo about configuration of extra server settings
docs: type about extra server args
gitea v1.15.10 is available
readme: gitea_lfs_enabled→gitea_lfs_server_enabled
since it is possible to run gitea with an other user defined in the ``{{ gitea_user }}`` variable, I built it in this command.
fixed backup failure
increase playbook version number
+ Added the variable ``gitea_actions_extra`` + Increased the Number for the simplified versions check
feat: Add support for Gitea Actions
fix(config): Fix name of the actionssection in the configuration file.
chore(repo): Setup dependabot to watch for new releases of Github Actions.
Bumps [robertdebock/galaxy-action](https://github.com/robertdebock/galaxy-action) from 1.2.0 to 1.2.1. - [Release notes](https://github.com/robertdebock/galaxy-action/releases) - [Commits](robertdebock/galaxy-action@1.2.0...1.2.1) --- updated-dependencies: - dependency-name: robertdebock/galaxy-action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [karancode/yamllint-github-action](https://github.com/karancode/yamllint-github-action) from 2.0.0 to 2.1.1. - [Release notes](https://github.com/karancode/yamllint-github-action/releases) - [Commits](karancode/yamllint-github-action@v2.0.0...v2.1.1) --- updated-dependencies: - dependency-name: karancode/yamllint-github-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…thub_actions/robertdebock/galaxy-action-1.2.1 Bump robertdebock/galaxy-action from 1.2.0 to 1.2.1
…thub_actions/karancode/yamllint-github-action-2.1.1 Bump karancode/yamllint-github-action from 2.0.0 to 2.1.1
+ Incremented simple version check + Added better error messages for chosing the wrong forgejo version SOLVE roles-ansible#106
Create better error message for forgejo releases
Adding variables to configure repository upload more easily
Repository Upload
Don't become for gpg verify (also for gitea)
Improve gpg permissions for forgejo
Refactor setting.Other and remove unused SHOW_FOOTER_BRANDING as announced in https://github.com/go-gitea/gitea/releases/tag/v1.20.0
Refactor setting.Other
Signed-off-by: Jens Timmerman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
for some reason this now needs to be set, otherwise my gitea binary just stops working, without an error message since latest gitea update.
relevant link go-gitea/gitea#25417