Version control systems are a category of software tools that help a software team manage changes.
Git is a very well supported open source project.
Git is a mature, actively maintained open source project
originally developed in 2005 by Linus Torvalds.
Introduction to version control with Git. Slides made for the Linguaggi e Ambienti Multimediali course at Politecnico di Torino, academic year 2011/2012.
What is Git | What is GitHub | Git Tutorial | GitHub Tutorial | Devops Tutori...Edureka!
This DevOps Tutorial on what is Git & what is GitHub ( Git Blog series: https://goo.gl/XS1Vux ) will let you know all about Version Control System & Version Control Tools like Git. You will learn all the Git commands to create repositories on your local machine & GitHub, commit changes, push & pull files. Also you will get your hands on with some advanced operations in Git like branching, merging, rebasing etc. Below are the topics covered in this tutorial:
1. Version Control Introduction
2. Why version Control?
3. Version Control Tools
4. Git & GitHub
5. Case Study: Dominion enterprises
6. What is Git?
7. Features of Git
8. What is a Repository?
9. Git Operations and Commands
Version control systems are a category of software tools that help a software team manage changes.
Git is a very well supported open source project.
Git is a mature, actively maintained open source project
originally developed in 2005 by Linus Torvalds.
Introduction to version control with Git. Slides made for the Linguaggi e Ambienti Multimediali course at Politecnico di Torino, academic year 2011/2012.
What is Git | What is GitHub | Git Tutorial | GitHub Tutorial | Devops Tutori...Edureka!
This DevOps Tutorial on what is Git & what is GitHub ( Git Blog series: https://goo.gl/XS1Vux ) will let you know all about Version Control System & Version Control Tools like Git. You will learn all the Git commands to create repositories on your local machine & GitHub, commit changes, push & pull files. Also you will get your hands on with some advanced operations in Git like branching, merging, rebasing etc. Below are the topics covered in this tutorial:
1. Version Control Introduction
2. Why version Control?
3. Version Control Tools
4. Git & GitHub
5. Case Study: Dominion enterprises
6. What is Git?
7. Features of Git
8. What is a Repository?
9. Git Operations and Commands
Recently one of our customers faced the challenge of fixing a production error in his desktop client application. The application is deployed in different versions and may of course be deployed to different customers with a different set of features. Although this scenario seems quite common nowadays, a lot of software companies are not ready to tackle this problem.
Github - Git Training Slides: FoundationsLee Hanxue
Slide deck with detailed step breakdown that explains how git works, together with simple examples that you can try out yourself. Slides originated from http://teach.github.com/articles/course-slides/
Author: https://twitter.com/matthewmccull
Through this tutorial, you can learn Git & GitHub fundamentals very easily. I have explained both theory and practical. I hope you will enjoy it. Happy Git.!!
Testing Persistent Storage Performance in Kubernetes with SherlockScyllaDB
Getting to understand your Kubernetes storage capabilities is important in order to run a proper cluster in production. In this session I will demonstrate how to use Sherlock, an open source platform written to test persistent NVMe/TCP storage in Kubernetes, either via synthetic workload or via variety of databases, all easily done and summarized to give you an estimate of what your IOPS, Latency and Throughput your storage can provide to the Kubernetes cluster.
With these slides we introduce the concept of source control and teach the core features to using Git, GitHub and BitBucket. You can find the accompanying video here. https://youtu.be/lZpNrCgGvuI
Git is a distributed revision control system that is widely used in the software development industry. The presentation was used in a lecture delivered in BITS-Pilani, India. The lecture served as a basic crash course on Git.
First, it sets off with a guide to install and configure git on various platforms.
Then, the basic working concepts of Git are explained.
This is followed by a detailed step-by-step guided demonstration of a sample workflow in Git.
Afterwards, Some auxillary commands that are frequently used are discussed briefly.
Finally, basic concepts of branching and merging are detailed.
The presentation ends with a few possible merge conflicts that occur in Git.
Recently one of our customers faced the challenge of fixing a production error in his desktop client application. The application is deployed in different versions and may of course be deployed to different customers with a different set of features. Although this scenario seems quite common nowadays, a lot of software companies are not ready to tackle this problem.
Github - Git Training Slides: FoundationsLee Hanxue
Slide deck with detailed step breakdown that explains how git works, together with simple examples that you can try out yourself. Slides originated from http://teach.github.com/articles/course-slides/
Author: https://twitter.com/matthewmccull
Through this tutorial, you can learn Git & GitHub fundamentals very easily. I have explained both theory and practical. I hope you will enjoy it. Happy Git.!!
Testing Persistent Storage Performance in Kubernetes with SherlockScyllaDB
Getting to understand your Kubernetes storage capabilities is important in order to run a proper cluster in production. In this session I will demonstrate how to use Sherlock, an open source platform written to test persistent NVMe/TCP storage in Kubernetes, either via synthetic workload or via variety of databases, all easily done and summarized to give you an estimate of what your IOPS, Latency and Throughput your storage can provide to the Kubernetes cluster.
With these slides we introduce the concept of source control and teach the core features to using Git, GitHub and BitBucket. You can find the accompanying video here. https://youtu.be/lZpNrCgGvuI
Git is a distributed revision control system that is widely used in the software development industry. The presentation was used in a lecture delivered in BITS-Pilani, India. The lecture served as a basic crash course on Git.
First, it sets off with a guide to install and configure git on various platforms.
Then, the basic working concepts of Git are explained.
This is followed by a detailed step-by-step guided demonstration of a sample workflow in Git.
Afterwards, Some auxillary commands that are frequently used are discussed briefly.
Finally, basic concepts of branching and merging are detailed.
The presentation ends with a few possible merge conflicts that occur in Git.
Diapositivas de la charla dada por la gente de uno21.com.ar (@luke_ar y @matitanio) en la UP, el día 21/08/2012. Próximamente en otras universidades :)
In this slide, I have a fully explanation about what is Git and why use it. I also give a fully explanation about the basic command that mostly use with git.
A practical step-by-step guide to Git, taking you through each phase of a project and explaining the use of Git at each step of the development process. Expect lots of how-to, but also some how-not-to, to avoid going down the wrong path.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
6. 1
2
3
Work ahead only if you dare...
Wait to run commands until instructed. Otherwise, you might get your working tree
into a wonky state.
Let us know if you get stuck.
Raise your hand if a command fails or if you get an unexpected result and don't know
how to fix it.
Ask questions.
Raise your hand if you have a question. We're here to help you learn.
Ground rules
@beckatodd | #WriteTheDocs
20. Basic workflow
1. create a branch
2. add our work (stage changes)
3. commit our work locally
4. push the branch to the remote repo (Bitbucket)
5. create a pull request (Bitbucket)
6. merge the changes into the master branch
7. pull changes from the remote repo
@beckatodd | #WriteTheDocs
21. Basic workflow
1. create a branch
6. merge the changes into the master branch
2. add our work (stage changes)
5. create a pull request (Bitbucket)
3. commit our work locally
4. push the branch to the remote repo (Bitbucket)
7. pull changes from the remote repo
@beckatodd | #WriteTheDocs
25. git -- help
Git’s documentation is
built in — try it for
yourself!
$ git --help
usage: git [--version] [--help] [-C <path>] [-c name=value]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p | --paginate | --no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
<command> [<args>]
These are common Git commands used in various situations:
start a working area (see also: git help tutorial)
clone Clone a repository into a new directory
init Create an empty Git repository or reinitialize an existing one
work on the current change (see also: git help everyday)
add Add file contents to the index
mv Move or rename a file, a directory, or a symlink
reset Reset current HEAD to the specified state
rm Remove files from the working tree and from the index
examine the history and state (see also: git help revisions)
27. Workspace
setup
Make a folder named
repos in a root folder.
$ mkdir repos && cd repos
repos/ $
macOS
$ cd c:
$ mkdir repos && cd repos
/c/repos/ $
Windows
37. • Clones a repository into a newly created directory
• Creates remote-tracking branches for each branch in the cloned repository
(visible using git branch -r),
• Creates and checks out an initial branch that is forked from the cloned
repository's currently active branch (typically master).
$ git clone <remote-info>
@beckatodd | #WriteTheDocs
38.
39.
40. git clone
Clones your fork into
its own directory
inside repos/.
$ git clone git@bitbucket.org:angie-
wallaby/learn-git-wtd-aus-2019.git
Cloning into 'learn-git-wtd-aus-2019'...
Warning: Permanently added the RSA host key for IP address
'18.205.93.0' to the list of known hosts.
remote: Counting objects: 13, done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 33 (delta 11), reused 0 (delta 0)
Receiving objects: 100% (13/13), 108.28 KiB | 1.14 MiBs,
done.
remote: Total 13 (delta 0), reuse 0 (delta0)
41. See what
happened
Switch to the learn-
git-wtd-aus-2019
directory, and list its
contents.
$ cd learn-git-wtd-aus-2019
exercise-one/ exercise-two/ LICENSE.txt resources/
$ ls
repos/learn-git-wtd-aus-2019/ $
$ open .
$ explorer .
43. We'll use three different arguments for the git remote command:
• -v to see the URLs of all remotes
• add <name> <url> to link to a new remote (upstream)
• set-url --push <name> <url> to disable the ability to push to the
upstream remote
$ git remote [various args]
@beckatodd | #WriteTheDocs
44. View remotes
Shows a list of
remotes associated
with your repo.
The -v argument
prints the URL after
the name.
$ git remote -v
origin git@bitbucket.org:angie-wallaby/learn-git-wtd-
aus-2019.git (fetch)
origin git@bitbucket.org:angie-wallaby/learn-git-wtd-
aus-2019.git (push)
45. Add
upstream
remote
Adds a connection to
the original repo,
which we're naming
upstream.
This command
requires the URL of
the main repo
(upstream).
$ git remote add upstream
git@bitbucket.org:beckytodd/learn-git-
wtd-aus-2019.git
46. View remotes
Shows a list of
remotes associated
with your repo.
The -v argument
prints the URL after
the name.
$ git remote -v
origin git@bitbucket.org:beckytodd/becky-learn-git-wtd-
aus-2019.git (fetch)
origin git@bitbucket.org:beckytodd/becky-learn-git-wtd-
aus-2019.git (push)
upstream git@bitbucket.org:beckytodd/learn-git-wtd-
aus-2019.git (fetch)
upstream git@bitbucket.org:beckytodd/learn-git-wtd-aus-
aus-2019.git (push)
47. Disable push
on upstream
remote
Updates the URL of
the remote named
upstream.
The --push argument
specifies that we
want to reset only the
URL associated with
the git push
command.
$ git remote set-url --push upstream
DISABLED
48. View remotes
Shows a list of
remotes associated
with your repo.
The -v argument
prints the URL after
the name.
$ git remote -v
origin git@bitbucket.org:beckytodd/becky-learn-git-wtd-
aus-2019.git (fetch)
origin git@bitbucket.org:beckytodd/becky-learn-git-wtd-
aus-2019.git (push)
upstream git@bitbucket.org:beckytodd/learn-git-wtd-
aus-2019.git (fetch)
upstream DISABLED (push)
49. git fetch
Gets updates from the
upstream repository.
$ git fetch upstream
From bitbucket.org:beckytodd/learn-git-wtd-aus-2019
* [new branch] master -> upstream/master
55. Always commit or stash changes before changing branches.
• <branch-name> specify a branch name to switch it
• -b <branch-name> to create a new branch AND switch to it
• -b <branch-name> <remote>/<branch> to create a new branch from
a branch on a specified remote (like upstream/master) AND switch to it
$ git checkout [various args]
🎉
56. • Cannot contain spaces
• Are case sensitive
• Should be short and descriptive
• Follow company style (for example, include issue numbers)
Branch names
57. git checkout
-b
Create and checkout a
new branch for your
work.
$ git checkout -b <name>-first-branch
upstream/master
Switched to a new branch 'angiew-first-branch'
Your branch is up to date with 'upstream/master'
59. Edit your file
Open the file that has
your name on it, and
make a change or two.
../exercise-one/<file-name>.md
---
title: "About berries"
---
# About berries
Berries are small fruits. They come in all shapes and
sizes. Scientists define berries as "a fruit produced from
the ovary of a single flower in which the outer layer of
the ovary wall develops into an edible fleshy portion
(pericarp)."
There are a number of fruts that you wouldn't normally
think of as berries, such as:
- bananas
61. Shows the status of the working tree:
• changed files
• deleted files
• new files (untracked)
• renamed (moved) files
• which files are staged (added)
$ git status
@beckatodd | #WriteTheDocs
62. git status
See the state of the
working tree.
$ git status
On branch angiew-first-branch
Your branch is up to date with 'upstream/master'
Changes not staged for commit:
(use "git add <file>..." to update what will be
committed)
(use "git checkout -- <file>..." to discard changes in
the working directory)
modified: exercise-one/<file-name>.md
no changes added to commit (use "git add"/or "git commit -
a")
63. • Adds the specified file(s) to staging
$ git add <file-name>
@beckatodd | #WriteTheDocs
64. git add
Add your file to stage
your changes.
$ git add exercise-one/<file-name>.md
On branch angiew-first-branch
Your branch is up to date with 'upstream/master'
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)
modified: exercise-one/<file-name>.md
$ git status
65. git reset
Remove your file from
staging.
$ git reset exercise-one/<file-name>.md
On branch angiew-first-branch
Your branch is up to date with 'upstream/master'
Changes not staged for commit:
(use "git add <file>..." to update what will be
committed)
(use "git checkout -- <file>..." to discard changes in
the working directory)
modified: exercise-one/<file-name>.md
no changes added to commit (use "git add"/or "git commit -
a")
$ git status
66. git add
Add your file to stage
your changes.
$ git add exercise-one/<file-name>.md
On branch angiew-first-branch
Your branch is up to date with 'upstream/master'
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)
modified: exercise-one/<file-name>.md
$ git status
67. • Write a commit message in editor, like Vim (no args)
• -m "Some message" write a commit message inline
$ git commit [various args]
@beckatodd | #WriteTheDocs
68. git commit
Use the -m argument
and add a commit
message in quotes.
$ git commit -m "Correcting spelling
errors and typos"
[angiew-first-branch 1ec8e60] Correcting spelling errors
and typos
1 file changed, 4 insertions(+), 4 deletions(-)
69. • Are associated with you
• Are kinda forever 💎
• Should be succinct and descriptive
• Follow company style (for example, include issue numbers)
• Line length limits may apply*
Commit messages
@beckatodd | #WriteTheDocs
70. • See the Git history in the command line
$ git log
@beckatodd | #WriteTheDocs
71. git log
See the git history in
the command line
interface.
$ git log
Commit d850bc4...(HEAD -> angiew-first-commit)
Author: Angie Wallaby <example-email@example.com>
Date: Wednesday November 13 12:03:58 2019 -0700
Correcting typos and spelling errors
Commit c845249... (upstream/master, origin/master, origin/
angiew-first-commit, origin/HEAD, master)
Merge: Becky Todd <btodd@atlassian.com>
Date: Wednesday November 13 13:01:14 2019 -0500
Merged wtd-class-set-up-merge-conflict into master
....
73. • Pushes the current branch to origin (no args)*
• <remote> <branch> specifies the exact remote and branch
$ git push [various args]
@beckatodd | #WriteTheDocs
74. git push
This command sends
a copy of all non-
pushed commits on
your branch to
Bitbucket.
$ git push origin <name>-first-branch
Enumerating objects: 7, done.
Counting objects: 100% (7.7), done.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 391 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
remote:
remote: Create pull request for angiew-first-branch:
remote: https://bitbucket.org/angie-wallaby/learn-git-
wtd-aus-2019/pull-requests/new?source=angiew-first-
branch&t=1
remote:
To bitbucket.org:angie-wallaby/learn-git-wtd-aus-2019.git
* [new branch] angiew-first-branch -> angiew-first-branch
76. • Use a descriptive title.
• Describe the changes you in the pull request.
• Indicate what you want the reviewers to review (for example, Please check
grammar and technical accuracy).
• Select reviewers who are responsible for approving and merging changes.
Pull requests
@beckatodd | #WriteTheDocs
79. • Downloads objects from origin, without making local changes (no args)
• <remote> specifies the remote to download objects from
$ git fetch [various args]
@beckatodd | #WriteTheDocs
80. git fetch
Gets updates from the
upstream repository
(including branches),
along with the objects
associated with the
updates.
Tip: git fetch does
not make local
changes.
$ git fetch upstream
remote: Counting objects: 9, done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 9 (delta 5), reused 0 (delta 0)
Unpacking objects: 100% (9/9), done.
From bitbucket.org:beckytodd/learn-git-wtd-aus-2019
* [new branch] dev-branch -> upstream/dev-branch
* [new branch] master -> upstream/master
81. • Incorporates objects into the current branch from origin (no args)*
• <remote> <branch> specifies the remote and branch to incorporate
objects from
$ git pull [various args]
@beckatodd | #WriteTheDocs
83. git push
This command sends
a copy of all non-
pushed commits on
your version of the
master branch to
Bitbucket.
$ git push origin master
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 8 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 406 bytes | 406.00 KiB/s, done.
Total 4 (delta 2), reused 0 (delta 0)
To bitbucket.org:beckytodd/becky-learn-git-wtd-aus-2019.git
0d85853..435eeb2 master -> master
91. • Lists all branches (no args)
• <name> creates a new branch*
• -r shows you the remote associated with a branch
• -d or -D deletes the specified branch
$ git branch [various args]
@beckatodd | #WriteTheDocs
92. Delete a
branch
$ git branch -d <name>-first-branch
Deleted branch angiew-first-branch was (d850bc4)
93. • Show changes for all files that are unstaged (no args)
• --cached shows changes for files that have been staged (diff between last
commit and the staged changes)
• <file-name> shows changes for a specific file
$ git diff [various args]
@beckatodd | #WriteTheDocs
94. • Stashes all local changes (no args)
• list shows a list of all of your stashes and associated branches
• apply stash@{#} applies the changes saved in a specified stash to your
current branch
• drop stash@{#} drops the stash from Git
$ git stash [various args]
@beckatodd | #WriteTheDocs
95. THERE'S SO MUCH MORE.
I'M STILL LEARNING GIT,
EVEN 7+ YEARS LATER...
@beckatodd | #WriteTheDocs