Acp#2583
Conversation
|
I have a question about this type of package which is, why do you only want to add this package to Termux and not to other distros? |
|
because this package for native termux, for the another distros, i will make it later, thank you. oh and are you the maintainer? |
|
Yes, but I am skeptical about the usefulness of a package that uses hundreds of lines of C code just to wrap the simple series of three commands git add .
git commit -m "message"
git pushI would like to see you also submit this package to another Linux distro so that the opinion of others can be compared to mine and we can see how many users a project like this is likely to have. @hastagaming I have another question, though, which is, why does your README contain directions written in the 2nd person with "your" describing this PR?
Is the only reason you are creating this PR because someone else told you to create this PR, or did you ask someone else how to create a PR to TUR? Specifically, @hastagaming , if you did ask someone else how to create a PR to TUR, did you ask that before or after you created the "acp" project? If you asked that after you created the "acp" project, then why does your project's initial README contain directions written in the second person instructing to create this PR? |
|
@robertkirkman sorry, i will remove it soon |
|
i've already remove the text |
|
Yes, but that does not answer the question I had which is, did that text get there because you asked someone else how to put a program on TUR first, then made the program second after that? |
|
i dont know, I was thinking about that |
|
I wonder about it just because there was once this infamous video where a tutorial told people how to make PRs and it resulted in a lot of PRs being created from people following the tutorial, https://socket.dev/blog/express-js-spam-prs-commoditization-of-open-source when I saw your README, it reminded me a lot of that so I wondered if this situation is similar. |
|
but, i not see the tutorial, i just say yo ai to make the README, but he gave me the tutorial, even though I didn't ask for it |
|
only README, not all acp |
|
I don't think that this package conforms the TUR's packag policy. TUR does not intend to package pure scripts, which are simply wrappers around existing programs. Whether this package is written in C or bash does not change the fact that it is a script. |
|
hmm, but there git backend, so is it not pure now? |
|
hey, are you the maintainer? |

ACP — Add Commit Push
A tiny CLI tool that simplifies the most common Git workflow:
git add . && git commit -m "message" && git push→acp "message"Features
-sflag--checkdetects.envfiles, API keys, and large binariesUsage
Building From Source
make sudo make install # or copy `acp` to a directory in $PATHOr use the prebuilt binary installer:
Requirements
LICENSE
apache 2.0
ACP (Add Commit Push) is a lightweight CLI wrapper around the most repetitive Git workflow: add, commit, and push. It's written in pure C, builds instantly, and includes modern features like tag management, security scanning, and safe mode to protect important branches. Perfect for Termux on Android where keyboard shortcuts are scarce.