00a3be8934
determine default branch ( #278 )
2020-06-16 13:41:01 -04:00
e52d022eb5
Fetch all history for all tags and branches when fetch-depth=0 ( #258 )
2020-05-27 09:54:28 -04:00
df86c829eb
fix readme ( #251 )
2020-05-20 10:20:52 -04:00
574281d34c
update readme
2020-03-19 22:17:25 -04:00
fbb30c60ab
Removed doc based on new changes ( #192 )
2020-03-19 22:03:41 -04:00
9a3a9ade82
persist core.sshCommand for submodules ( #184 )
...
* persist core.sshCommand for submodules
* update verbiage; add comments
* fail when submodules or ssh-key and fallback to REST API
2020-03-12 11:42:38 -04:00
b2e6b7ed13
add ssh support ( #163 )
2020-03-11 15:55:17 -04:00
422dc45671
add support for submodules ( #173 )
2020-03-05 14:21:59 -05:00
77904fd431
Handle submodules with SSH URLs ( #140 )
...
* Handle submodules with SSH URLs
This is just a documentation change, explaining how to fix submodules
that are configured to use SSH URLs instead of HTTPS URLs. Spent a while
banging my head on the wall and hope this saves someone else the pain.
This is helpful for teams that use the SSH protocol for local
development so don't want to change the mechanism that pulls in the
submodules. Using `insteadOf` seems a bit nicer than than setting up a
deploy keypair.
* SSH submodules
Co-authored-by: Chris Patterson <chrispat@github.com>
2020-02-13 14:44:37 -05:00
bc50a995b8
Add link to doc for creating and using encyrpted secrets ( #123 )
2020-01-03 12:32:17 -05:00
f466b96953
improve summary ( #127 )
2020-01-02 15:40:10 -05:00
c85684db76
example fetch all history for all tags and branches ( #115 )
2019-12-16 10:45:02 -05:00
299dd5064e
add more scenarios ( #112 )
2019-12-13 16:39:47 -05:00
722adc63f1
update examples to reference v2 tag ( #110 )
2019-12-13 00:00:48 -05:00
c170eefc26
add input persist-credentials ( #107 )
2019-12-12 13:49:26 -05:00
a572f640b0
fallback to REST API to download repo ( #104 )
2019-12-12 13:16:16 -05:00
cab31617d8
Document update: Checkout PR head sha ( #102 )
2019-12-10 11:17:38 -05:00
5881116d18
Update README.md
2019-12-05 22:10:31 -05:00
7990b10a0c
Update description ( #65 )
2019-12-04 23:43:03 -05:00
01a434328a
document scenario: checkout the head commit of a PR ( #90 )
2019-12-04 10:12:10 -05:00
4817b449b0
clarify name with owner ( #87 )
2019-12-03 16:47:19 -05:00
cc70598ce8
Update README.md
2019-12-03 11:35:57 -05:00
8461dbfed3
update readme ( #82 )
2019-12-03 11:26:12 -05:00
e347bba93b
Convert checkout to a regular action ( #70 )
2019-12-03 10:28:59 -05:00
50fbc622fc
Reverted Changes to Git Config and Authentication ( #64 )
...
v1.2.0 Release - Reverted changes to git just works authentication
2019-11-21 11:04:30 -05:00
e8bd1dffb6
Update help docs link ( #68 )
2019-11-20 13:36:26 -05:00
0b496e91ec
Upgrade checkout to v1.1.0 to better support scripting git. ( #56 )
...
* Upgrade checkout to v1.1.0 to better support scripting git.
* add changelog
* Update README.md
* Add local testing yaml
* Add Status Badge to readme
2019-10-25 10:52:59 -04:00
0963d3b35f
add docs about checking out the triggering ref ( #21 )
...
* add docs about checking out the triggering ref
* clarify checkout behavior
2019-09-05 11:42:49 -04:00
a14471d838
clarify language on working directory ( #9 )
...
* clarify language
I guess this action doesn't technically make sure that my working directory is `$GITHUB_WORKSPACE`, so this might be more precise?
* fix repetition
2019-08-21 21:39:05 -04:00
cacfc4155d
Change version to node-version ( #12 )
...
version is deprecated and replaced by node-version
2019-08-16 10:59:11 -04:00
6e6328ef28
README: Environment variable typo fix ( #11 )
2019-08-16 10:56:22 -04:00
b4b537b06a
clarify default checkout sha ( #10 )
...
this is trivial for `on: push`, but might be helpful to remind readers that this ain't always so for other events.
Hence the link to the docs.
2019-08-13 10:53:03 -04:00
af513c7a01
actions to steps
2019-07-25 21:30:48 -04:00
bf4af63534
Add docs ( #2 )
...
* Update README.md
* Create LICENSE
* Update README.md
2019-07-23 15:32:03 -04:00
44679f67d2
Initial commit
2019-07-19 13:15:34 -04:00
eric sciple