add-and-commit | :octocat: Automatically commit changes made in your workflow run directly to your repo | Continous Integration library

by EndBug TypeScript Version: v9.1.3 License: MIT

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | add-and-commit Summary

add-and-commit is a TypeScript library typically used in Devops, Continous Integration applications. add-and-commit has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

You can use this GitHub Action to commit changes made in your workflow run directly to your repo: for example, you use it to lint your code, update documentation, commit updated builds, etc...

Support

Quality

Security

License

Reuse

Support

add-and-commit has a medium active ecosystem.

It has 866 star(s) with 100 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 156 have been closed. On average issues are closed in 7 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of add-and-commit is v9.1.3

Quality

add-and-commit has 0 bugs and 0 code smells.

Security

add-and-commit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

add-and-commit code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

add-and-commit is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

add-and-commit releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of add-and-commit

Get all kandi verified functions for this library.

add-and-commit Key Features

No Key Features are available at this moment for add-and-commit.

add-and-commit Examples and Code Snippets

No Code Snippets are available at this moment for add-and-commit.

Community Discussions

Trending Discussions on add-and-commit

Git workflow with many modified files not for check-in?

GitHub Actions to use variables set from shell

How to run git diff in github actions

function to modify bash command based on condition

QUESTION

Git workflow with many modified files not for check-in?

Asked 2021-Nov-11 at 15:36

Using git and a workflow where I have many loose changes that are not intended for check-in. Is there a good git way to manage those not-for-check-in modified files?

In my project, we have about 700,000 source files. I'd call it a larger project.

When I am working on fixing a bug or implementing a feature, I will quite frequently end up with many files that I have made ancillary edits. Such as debugging instrumentation, or alternative implementation, or an expensive check for a never-happen situation that once appears to have happened in the wild and I want to catch it if it ever happens on my machine, or clang-format because the original had goofy formatting.

To commit my good changes, I'll branch, I carefully add the relevant files and commit those. (Followed by a push of my changes. Make a PR. Get code review approval. Jenkins builds on all the dozen different target platforms, and runs the test suite. Then I merge my branch into main.)

Probably a fairly typical workflow... except for that I have many (1000+) not-for-check-in files that I want to keep modified in my worktree, but not merge those into main. That latter part is probably atypical.

With Perforce, I would add my not-for-check-in files into a not-for-check-in changelist and park them there. They'd be out of the way, and I could not accidentally pull one of those "tainted" files without taking steps to move it out of the not-for-check-in changelist.

So far, my git tactic of being super-duper careful has worked, but seems fraught with peril. I maintain a stash.txt file that has a list of my not-for-check-in files, and frequently stash them to temporarily get them out of the way, do my git things (making branches, fetch, merge, push, whatever), and stash pop them back in my worktree. Seems janky, manual, and error prone; high cognitive load. Has to be a better way.

(I have not run into the scenario when I have a single file that has both good changes and not-for-check-in changes. If/when I do, I am aware of how to add-and-commit hunks of changes.)

I have tried the tactic of making a branch, add-and-commit both my good changes and not-for-check-in changes. Then cherry pick the good changes for what should go into main. That scales poorly with the 1000s of not-for-check-in files that need to be sifted through.

Any advice or guidance is appreciated.

...

ANSWER

Answered 2021-Nov-11 at 15:36

Using git worktree, I would work with two separate working tree (from the same cloned repository: no need to clone twice)

one for the work in progress, with many files not to be added
one for reporting the work which needs to be added: no stash to maintain in this one.

Does Git support multiple concurrent index (or staging), which would be the analog to Perforce changelist?

Not really: it would be easier to make multiple commits:

one your PR
one for the rest

And push only the first commit (for PR).

From the discussion:

"How can I make Git "forget" about a file that was tracked, but is now in .gitignore?" uses git update-index --skip-worktree, which I don't find very practical, or easier than git stash.
git rebase -i follwoed by git push : should be enough

Source https://stackoverflow.com/questions/69928486

QUESTION

GitHub Actions to use variables set from shell

Asked 2021-Jul-14 at 18:22

Goal:

In GitHub Actions, to define my commit message dynamically from shell:

...

ANSWER

Answered 2021-Jul-14 at 18:22

If you want to reference an environment variable set using the $GITHUB_ENV environment file in the arguments to another task, you'll need to use workflow syntax to access the appropriate key of the top level env key, like this:

Source https://stackoverflow.com/questions/68381640

QUESTION

How to run git diff in github actions

Asked 2021-Jan-28 at 20:44

I am getting this:

...

ANSWER

Answered 2021-Jan-28 at 20:44

If you take a look at the documentation for the actions/checkout@v2 action, you'll see it performs a shallow clone with a single revision by default:

Source https://stackoverflow.com/questions/65944700

QUESTION

function to modify bash command based on condition

Asked 2020-Oct-26 at 13:41

The current state of the function is like:

...

ANSWER

Answered 2020-Oct-26 at 13:41

You don't need to use echo so:

Source https://stackoverflow.com/questions/64537435

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install add-and-commit

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: