Re: pt_BR builds fails only locally
| From: | André L F S Bacci | Date: | Thu, 15 Apr 2021 14:13:11 +0000 |
| Subject: | Re: pt_BR builds fails only locally | ||
| References: | 1 2 3 4 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969387899@lists.php.net to get a copy of this message | ||
On Thu, Apr 15, 2021 at 11:24 AM Sergey Panteleev <sergey@s-panteleev.ru>
wrote:
> I haven't figured out how to commit directly from the editor yet (if
> someone has any ideas, I’ll be glad to hear),
>
With GitHub security measures, the only way I can think of is to upload a
private cert on the editor, but this is a big security risk.
> so my workflow is: edit files on edit.php.net, create a patch, download
> it, then apply locally and push to GitHub.
>
You can automatise this, to make this the most comfortable possible. Say,
in the editor, there is a button to push send something edited. This button:
1. Prepare a local patch and a commit message.
2. Show a page/message with the commands to execute on a local machine:
2.1 Download the patch and the message
2.2 Push the specific patch and message to GitHub (possible without a git
clone?)
2.3 Remove these two files
3. In the same page/message, make it possible to copy these commands to
clipboard and have a check box with the option to always copy commands,
with persistence.
See test.sh and push.sh on
https://github.com/alfsb/phpdoc/tree/main/translator-utils
for my take on
this.
André L F S Bacci