You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Amelchev Nikita (Jira)" <ji...@apache.org> on 2022/05/05 14:49:00 UTC
[jira] [Comment Edited] (IGNITE-16895) Update documentation with GitHub Actions
[ https://issues.apache.org/jira/browse/IGNITE-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532282#comment-17532282 ]
Amelchev Nikita edited comment on IGNITE-16895 at 5/5/22 2:48 PM:
------------------------------------------------------------------
Merged into the master.
[~mmuzaf], thank you for the review!
was (Author: nsamelchev):
Merged into the master.
> Update documentation with GitHub Actions
> ----------------------------------------
>
> Key: IGNITE-16895
> URL: https://issues.apache.org/jira/browse/IGNITE-16895
> Project: Ignite
> Issue Type: Task
> Reporter: Amelchev Nikita
> Assignee: Amelchev Nikita
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> GitHub Actions can be used to update documentation for released Ignite versions.
> For now, this is a complex manual work that requires understanding all the intermediate steps: [wiki|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs].
> I propose to automatize this and give an ability to update documentation on a push event to a released branch.
> ASF GitHub Actions Policy allows automated services to push changes related to documentation: [policy|https://infra.apache.org/github-actions-policy.html].
> Write access is [required|https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow] to run the update. So, only committers can run workflows manually.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)