actions/github-action-push-to-another-repository
1
0
Fork 0
mirror of https://github.com/cpina/github-action-push-to-another-repository.git synced 2024-12-22 08:06:10 -07:00
Code Issues Packages Projects Releases Wiki Activity

Not being able to develop: add warning

Browse Source
This commit is contained in:
Carles Pina i Estany 2024-09-15 20:10:15 +01:00
parent 07c4d7b3de
commit 39128b58f7
No known key found for this signature in database
GPG Key ID: A802884F60A55F81
2 changed files with 33 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
.github/ISSUE_TEMPLATE/bug_report.md vendored
View File

@ -7,10 +7,27 @@ assignees: ''
--- ---
> [!WARNING]
> TL;DR: this repository is not maintained for any new development. I plan to
> fix issues if they arise due to changes on GitHub, to minimise disruption of
> existing usage.
>
> My circumstances changed since I started the GitHub Action in 2020. I am not
> able to add functionality to it or fix issues.
>
> The action is 175 lines of shell script. Feel free to fork it and modify it
> for your own use case.
>
> If you create a fork that might replace this one, I will add a note in the
> documentation and the README.md. Please, open an issue and I will do it.
Suggestion: read carefully the GitHub Action output. It might contain information that might help fixing the problem. If not please keep opening the bug report. Suggestion: read carefully the GitHub Action output. It might contain information that might help fixing the problem. If not please keep opening the bug report.
The documentation might have information on what you could do to fix the problem. The [documentation](https://github.com/cpina/push-to-another-repository-docs)
might have information on what you could do to fix the problem. See the [FAQ](https://cpina.github.io/push-to-another-repository-docs/faq.html)
<!--
**Copy-paste the output of the GitHub Action** **Copy-paste the output of the GitHub Action**
Full output might contain useful information including the git command, git output and settings used. It also helps to search for the problem later on. Full output might contain useful information including the git command, git output and settings used. It also helps to search for the problem later on.
@ -18,3 +35,4 @@ Full output might contain useful information including the git command, git outp
**URL to the execution** **URL to the execution**
Paste the URL of the execution where it's possible to see the problem. This will help me to see the configuration and the output in more context. Paste the URL of the execution where it's possible to see the problem. This will help me to see the configuration and the output in more context.
-->

14
README.md
View File

@ -1,5 +1,19 @@
# github-action-push-to-another-repository # github-action-push-to-another-repository
> [!WARNING]
> TL;DR: this repository is not maintained for any new development. I plan to
> fix issues if they arise due to changes on GitHub, to minimise disruption of
> existing usage.
>
> My circumstances changed since I started the GitHub Action in 2020. I am not
> able to add functionality to it or fix issues.
>
> The action is 175 lines of shell script. Feel free to fork it and modify it
> for your own use case.
>
> If you create a fork that might replace this one, I will add a note in the
> documentation and the README.md. Please, open an issue and I will do it.
See the extensive documentation in https://cpina.github.io/push-to-another-repository-docs/ (includes examples, FAQ, troubleshooting, etc.). See the extensive documentation in https://cpina.github.io/push-to-another-repository-docs/ (includes examples, FAQ, troubleshooting, etc.).
GitHub repository of the documentation: https://github.com/cpina/push-to-another-repository-docs GitHub repository of the documentation: https://github.com/cpina/push-to-another-repository-docs