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

fix rebar dependency specification #900

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

galdor
Copy link

@galdor galdor commented Aug 11, 2020

Rebar3 emits a warning for "raw" git dependency versions, and expects a
tuple indicating what the version actually is (a branch, tag or ref).

This warning propagates to any software directly or indirectly using
Gun.

This syntax also works with rebar2
(https://github.com/rebar/rebar/blob/master/src/rebar_deps.erl#L608).

Rebar3 emits a warning for "raw" git dependency versions, and expects a
tuple indicating what the version actually is (a branch, tag or ref).

This warning propagates to any software directly or indirectly using
Gun.

This syntax also works with rebar2
(https://github.com/rebar/rebar/blob/master/src/rebar_deps.erl#L608).
@essen
Copy link
Member

essen commented Aug 11, 2020

@essen
Copy link
Member

essen commented May 12, 2023

That's fine for commits but will this work fine for tags and branches too? Is there some expectations around differentiating ref/branch/tag in the rebar.config?

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

Successfully merging this pull request may close these issues.

None yet

2 participants