bgforgenet/BGforge poify/unpoify
Update Gettext POT template from source language, extract translations from PO files, commit and push the files.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 16, 2026
- License
- None
Pinned Snippet
uses: bgforgenet/msg2po@e4d1960bb871c9f0b3b4a2fcd4dd197f8ee25d5f # v1.6.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| poify | run poify and msgmerge | no | false |
| poify_commit | commit poify result | no | true |
| poify_trigger_unpoify_on_change | Actions cannot self-trigger. If poify+msgmerge resulted in PO update, which was commited into the repository, it will not trigger unpoify. That gets translation files out of sync with POs for some time. This setting enables instant unpoify after poify+merge, keeping translation files synced. | no | true |
| unpoify | run unpoify | no | false |
| unpoify_commit | commit unpoify result | no | true |
| dir2msgstr | load manually updated translations into POs | no | false |
| dir2msgstr_commit | commit dir2msgstr result | no | true |
| push | push commits | no | true |
| single_commit | make just one commit combining all changes made by the action | no | false |
| handle_charsets | run handle-charsets | no | false |
| handle_charsets_tra_path | handle-charsets source tra path | no | "" |
| handle_charsets_out_path | handle-charsets converted tra path | no | "" |
| handle_charsets_from_utf8 | handle-charsets from_utf8 | no | false |
| handle_charsets_split_console | handle-charsets split_console | no | false |
| handle_charsets_commit | handle-charsets commit | no | true |
Outputs
no outputs