You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| `jobs.qiita.steps[*].with.mapping_filepath` | Specify any file path in which you want to put the mapping file | false | `mapping.txt` |
79
+
| `jobs.qiita.steps[*].with.strict` | Specify whether the strict mode is on or off | false | `false` |
77
80
78
81
[^1]: Only in case you set the secret environment variable name as `QIITA_ACCESS_TOKEN` at the previous step.
79
82
80
83
**WARNING:** Please do not set the version to `@main` at the `jobs.qiita.steps[*].uses` section for a production use because the specification is subject to change, and the latest codes potentially contain bugs. It is highly recommended to set the latest tagged version, which can be accessible at the [Tags page](/../../tags).
81
84
85
+
#### About the strict mode
86
+
The strict mode determines whether your article will be published newly or not even if the corresponding article on Qiita is not found and your article file on your repository is MODIFIED (not ADDED). When the strict mode is on (`jobs.qiita.steps[*].with.strict` is set to `true`), your article won’t be published newly if the mapping file is incomplete, the corresponding article on Qiita is not found, and your article file is MODIFIED. Otherwise, your article will be published newly.
87
+
88
+
If your mapping information is not fully filled, it is recommended to set `true` because if `false` your article can be going to be published newly even if your articles exist on Qiita. But note that if your new article failed to publish to Qiita for some reason (The Qiita API is down or your article is invalid), your article will never be published as long as you don’t publish manually. Consider setting `jobs.qiita.steps[*].with.strict` to `false` to avoid it.
0 commit comments