281 Search results for "diff context"

an easily understandable visualization of dependency changes with a rich diff on the "Files Changed" tab of a pull request. Dependency review

This value can include expressions and can reference the github and inputs contexts. Example of run-name run-name: Deploy to ${{ inputs.deploy_target }} by

branches. requiredStatusCheckContexts ([String]) List of required status check contexts that must pass for commits to be accepted to matching branches. requiredStatusChecks

development workflows by enabling developers to address issues directly in the context of their codebase. Code scanning will also display alerts in pull request

addPullRequestReviewComment mutation. position (Int) The line index in the diff to comment on. Upcoming Change on 2023-10-01 UTC Description: position will

diffs, in the top-right corner of the diff view, click . To change how the entire diff is displayed, under "Diff display", select Unified or Split

access env variable values using runner environment variables or using contexts. The example above shows three custom variables being used as runner environment

optimize an author's ability to quickly provide context when they request a human review that requires sharing context of the changes that were made. It may help

quickly provide context to the human reviewers of the pull request. When reviewing a pull request it is valuable to understand context such as why changes

Description | | --- | --- | | git status | List all new or modified files | | git diff | Show file differences that haven't been staged | If you are frequently