Search Results for "code review"

This repository is for the GitHub Action to run a Super-Linter. It is a simple combination of various linters, written in bash, to help validate your source code. The super-linter finds issues and reports them to the console output. Fixes are suggested in the console output but not automatically fixed, and a status check will show up as failed on the pull request. The design of the Super-Linter is currently to allow linting to occur in GitHub Actions as a part of continuous integration...

These bash shell scripts are intended to iteratively load executable files via symbolic links and echo output to a log file for later review. These bash shell scripts rely on a directory structure intended to group testing and reporting executable files by project, target platform, and version.

Often I have seen some Huge Maintenance Projects it is always very difficult to track the incremental files for each release and If we want to do that we need to checkout both the branches and use some UI based tool to get the diff of the files finally we end up waiting in front of the PC for a long time and do this job. In many cases we spend more than 2 hrs/day. The time increases if there are more such parallel releases and at the end of the day 1 developer does it as full time job and...

...And also important to note to be extra careful when fixing public APIs! A manual review is always needed to verify that nothing has been broken.