-
Notifications
You must be signed in to change notification settings - Fork 7.4k
Git Tips
(This feature has been temporarily disabled)
The Sphinx-generated documentation from a PR test run can be found at:
http://zephyr-logs.s3-website-us-east-1.amazonaws.com/pull-requests/zephyrproject-rtos/zephyr/{PULL_REQUEST}/doc/
and the Doxygen-generated API documentation can be found at:
http://zephyr-logs.s3-website-us-east-1.amazonaws.com/pull-requests/zephyrproject-rtos/zephyr/{PULL_REQUEST}/api/
From within a cloned zephyr git repo on your host computer:
$ git for-each-ref --sort=taggerdate --format '%(refname) %(taggerdate)' refs/tags \
| grep "zephyr-v"
refs/tags/zephyr-v1.0.0 Mon Feb 8 21:41:31 2016 -0500
refs/tags/zephyr-v1.1.0 Sat Mar 5 07:47:21 2016 -0500
refs/tags/zephyr-v1.2.0 Sat Apr 2 12:06:57 2016 -0400
refs/tags/zephyr-v1.3.0 Mon May 2 21:16:49 2016 -0400
refs/tags/zephyr-v1.4.0 Fri Jun 3 12:30:11 2016 -0400
refs/tags/zephyr-v1.5.0 Fri Aug 26 17:40:50 2016 -0400
refs/tags/zephyr-v1.6.0 Sat Dec 3 08:32:39 2016 -0500
refs/tags/zephyr-v1.7.0 Sat Mar 11 17:25:22 2017 +0100
refs/tags/zephyr-v1.6.1 Mon May 15 08:59:35 2017 -0400
refs/tags/zephyr-v1.7.1 Mon May 15 09:00:23 2017 -0400
refs/tags/zephyr-v1.8.0 Thu Jun 15 22:47:33 2017 -0400
If you want to checkout the patches for a PR (or more specifically for a commit of a PR) you create branch in your working repo and pull the developer's branch::
$ git pull https://github.com/USER/PROJECT_REPO BRANCH_NAME
Since folks tend to create a branch in their working repo specific to a PR (and that branch is listed in the PR to the project’s master branch), you can do, for example::
$ git checkout -b test-docs
$ git pull https://github.com/jukkar/zephyr zep-2308-net-api-doc-missing
Zephyr Project Home | Documentation Home | Mailing lists