Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some suggestions about Google repo #2

Open
kaori-seasons opened this issue Jan 28, 2019 · 2 comments
Open

Some suggestions about Google repo #2

kaori-seasons opened this issue Jan 28, 2019 · 2 comments

Comments

@kaori-seasons
Copy link

kaori-seasons commented Jan 28, 2019

By rolling back your commit record, you find the following things

  • Repo use command is not skilled, modify too much
    Recommended reference to the official documentation
  • Some common bugs in google respo, it is recommended to look at the discussion group below him.
    Here is the Google repo on the bug details page
  • Finally, this is a summary of the use of Google repo.
@kaori-seasons
Copy link
Author

kaori-seasons commented Jan 28, 2019

Hello ,Here are the things you need to pay attention to:

Local Manifests

Additional remotes and projects may be added through local manifest files stored in $TOP_DIR/.repo/local_manifests/*.xml.

For example:

$ ls .repo/local_manifests
local_manifest.xml
another_local_manifest.xml

$ cat .repo/local_manifests/local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project path="manifest"
           name="tools/manifest" />
  <project path="platform-manifest"
           name="platform/manifest" />
</manifest>

@kj415j45
Copy link
Member

Thanks for your suggestions.

I have used local manifest to create a development environment. What I push to snippets/kjBot.xml is the production version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants