You can clone a repository from GitHub.com to your local computer, or to a codespace, to make it easier to fix merge conflicts, add or remove files, and push larger commits. When you clone a repository, you copy the repository from GitHub.com to your local machine, or to a remote virtual machine when you create a codespace. For more information about cloning to a codespace, see "Creating a codespace for a repository."
You can clone a repository from GitHub.com to your local computer to make it easier to fix merge conflicts, add or remove files, and push larger commits. When you clone a repository, you copy the repository from GitHub.com to your local machine.
To clone a repository locally, use the repo clone subcommand. Replace the repository parameter with the repository name. For example, octo-org/octo-repo, monalisa/octo-repo, or octo-repo. If the OWNER/ portion of the OWNER/REPO repository argument is omitted, it defaults to the name of the authenticating user.
To clone your repository using the command line using HTTPS, under "Quick setup", click . To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click SSH, then click .
Here we'll examine the git clone command in depth. git clone is a Git command line utility which is used to target an existing repository and create a clone, or copy of the target repository. In this page we'll discuss extended configuration options and common use cases of git clone. Some points we'll cover here are:
If a project has already been set up in a central repository, the git clone command is the most common way for users to obtain a development copy. Like git init, cloning is generally a one-time operation. Once a developer has obtained a working copy, all version control operations and collaborations are managed through their local repository.
An example demonstrating using git clone can be found on the setting up a repository guide. The example below demonstrates how to obtain a local copy of a central repository stored on a server accessible at example.com using the SSH username john:
The first command initializes a new Git repository in the my-project folder on your local machine and populates it with the contents of the central repository. Then, you can cd into the project and start editing files, committing snapshots, and interacting with other repositories. Also note that the .git extension is omitted from the cloned repository. This reflects the non-bare status of the local copy.
The -branch argument lets you specify a specific branch to clone instead of the branch the remote HEAD is pointing to, usually the main branch. In addition you can pass a tag instead of branch for the same effect.
Similar to git init --bare, when the -bare argument is passed to git clone, a copy of the remote repository will be made with an omitted working directory. This means that a repository will be set up with the history of the project that can be pushed and pulled from, but cannot be edited directly. In addition, no remote branches for the repo will be configured with the -bare repository. Like git init --bare, this is used to create a hosted repository that developers will not edit directly.
Passing the --mirror argument implicitly passes the --bare argument as well. This means the behavior of --bare is inherited by --mirror. Resulting in a bare repo with no editable working files. In addition, --mirror will clone all the extended refs of the remote repository, and maintain remote branch tracking configuration. You can then run git remote update on the mirror and it will overwrite all refs from the origin repo. Giving you exact 'mirrored' functionality.
The problem I'm having is when I copy the graphics to a new Graphics layer for the second map, they disappear from the first map. I'm seeing in Flex that there is a "graphic.Geometry.Clone()" function that allows one to clone points. Is there an equivalent in JSAPI? Or is there any other way I can copy (not cut) points from one map to the other?
The structured clone algorithm copies complex JavaScript objects. It is used internally when invoking structuredClone(), to transfer data between Workers via postMessage(), storing objects with IndexedDB, or copying objects for other APIs.
\n The structured clone algorithm copies complex JavaScript objects.\n It is used internally when invoking structuredClone(), to transfer data between Workers via postMessage(), storing objects with IndexedDB, or copying objects for other APIs.\n
Note: For performance reasons, the dynamic state of certain form elements (e.g., user data typed into textarea and user selections made to a select) is not copied to the cloned elements. When cloning input elements, the dynamic state of the element (e.g., user data typed into text inputs and user selections made to a checkbox) is retained in the cloned elements.
Normally, any event handlers bound to the original element are not copied to the clone. The optional withDataAndEvents parameter allows us to change this behavior, and to instead make copies of all of the event handlers as well, bound to the new copy of the element. As of jQuery 1.4, all element data (attached by the .data() method) is also copied to the new copy.
Note: Using .clone() has the side-effect of producing elements with duplicate id attributes, which are supposed to be unique. Where possible, it is recommended to avoid cloning elements with this attribute or using class attributes as identifiers instead.
Types that are Copy should have a trivial implementation of Clone. More formally:if T: Copy, x: T, and y: &T, then let x = y.clone(); is equivalent to let x = *y;.Manual implementations should be careful to uphold this invariant; however, unsafe codemust not rely on it to ensure memory safety.
The term cloning describes a number of different processes that can be used to produce genetically identical copies of a biological entity. The copied material, which has the same genetic makeup as the original, is referred to as a clone. Researchers have cloned a wide range of biological materials, including genes, cells, tissues and even entire organisms, such as a sheep.
Natural clones, also known as identical twins, occur in humans and other mammals. These twins are produced when a fertilized egg splits, creating two or more embryos that carry almost identical DNA. Identical twins have nearly the same genetic makeup as each other, but they are genetically different from either parent.
Ultimately, the adult female gives birth to an animal that has the same genetic make up as the animal that donated the somatic cell. This young animal is referred to as a clone. Reproductive cloning may require the use of a surrogate mother to allow development of the cloned embryo, as was the case for the most famous cloned organism, Dolly the sheep.
It was not until 1996, however, that researchers succeeded in cloning the first mammal from a mature (somatic) cell taken from an adult animal. After 276 attempts, Scottish researchers finally produced Dolly, the lamb from the udder cell of a 6-year-old sheep. Two years later, researchers in Japan cloned eight calves from a single cow, but only four survived.
Besides cattle and sheep, other mammals that have been cloned from somatic cells include: cat, deer, dog, horse, mule, ox, rabbit and rat. In addition, a rhesus monkey has been cloned by embryo splitting.
In 1998, scientists in South Korea claimed to have successfully cloned a human embryo, but said the experiment was interrupted very early when the clone was just a group of four cells. In 2002, Clonaid, part of a religious group that believes humans were created by extraterrestrials, held a news conference to announce the birth of what it claimed to be the first cloned human, a girl named Eve. However, despite repeated requests by the research community and the news media, Clonaid never provided any evidence to confirm the existence of this clone or the other 12 human clones it purportedly created.
In 2004, a group led by Woo-Suk Hwang of Seoul National University in South Korea published a paper in the journal Science in which it claimed to have created a cloned human embryo in a test tube. However, an independent scientific committee later found no proof to support the claim and, in January 2006, Science announced that Hwang's paper had been retracted.
760c119bf3