dokuwiki: add ability to checkout custom theme repo #21
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
renovate
waiting on upstream
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
CCCHH/ansible-infra!21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "eh22-wiki-design"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Aside from this one thing, looks good!
@ -45,0 +53,4 @@single_branch: truetrack_submodules: trueaccept_hostkey: trueaccept_newhostkey: trueLet's not do that, but encourage just using
https://-clone URLs instead?yeah the hostkey stuff makes sense.
but single branch makes sense as a shallow copy of the repo is sufficient to apply the theme, and if a theme uses submodules, these need to be pulled in as well
Oh yeah ofc, I'm just talking about:
Forgejo doesn't allow highlighting specific ranges, so it just picked four lines it seems. :/
@ -4,2 +4,4 @@dokuwiki__php_user: "www-data"dokuwiki__nginx_user: "nginx"dokuwiki__custom_theme_git_url: ""dokuwiki__custom_theme_name: ""Oh also please document both these options in the README.
@ -45,0 +45,4 @@- name: checkout custom theme git repobecome: trueansible.builtin.git:ansible-lintis failing as this module-use isn't idempotent. Let's introduce the following option and attribute for the module, to make it theoretically possible to be idempotent:And then set for
ansible.builtin.git:Documentation for
dokuwiki__custom_theme_versionwould be: version (git branch, tag, ...) to checkout, defaultmainLGTM! Thanks!
Merged via
CCCHH/ansible-infra@7271426502merged by squash
@dario wrote in #21 (comment):
You know, that Forgejo has a button for that!?
@jtbx wrote in #21 (comment):
yes, but the merge commit isnt verified if done via the webinterface
Pull request closed