rebranding: update links rebar/rebar3 -> erlang/rebar3

CONTRIBUTING.md

@@ -23,7 +23,7 @@ All files without specific headers can safely be assumed to be under Apache
 
 ## Submitting a Bug
 
-Bugs can be submitted to the [Github issue page](https://github.com/rebar/rebar3/issues).
+Bugs can be submitted to the [Github issue page](https://github.com/erlang/rebar3/issues).
 
 Rebar3 is not perfect software and will be buggy. When submitting a bug, be
 careful to know the following:
@@ -58,7 +58,7 @@ Before requesting or implementing a new feature, please do the following:
 
 - Take a look at our [list of plugins](http://www.rebar3.org/docs/using-available-plugins)
   to know if the feature isn't already supported by the community.
-- Verify in existing [tickets](https://github.com/rebar/rebar3/issues) whether
+- Verify in existing [tickets](https://github.com/erlang/rebar3/issues) whether
   the feature might already is in the works, has been moved to a plugin, or
   has already been rejected.
 

README.md

@@ -1,6 +1,6 @@
 # Rebar3
 
-[![Build Status](https://travis-ci.org/rebar/rebar3.svg?branch=master)](https://travis-ci.org/rebar/rebar3) [![Windows build status](https://ci.appveyor.com/api/projects/status/yx4oitd9pvd2kab3?svg=true)](https://ci.appveyor.com/project/TristanSloughter/rebar3)
+[![Build Status](https://travis-ci.org/erlang/rebar3.svg?branch=master)](https://travis-ci.org/erlang/rebar3) [![Windows build status](https://ci.appveyor.com/api/projects/status/yx4oitd9pvd2kab3?svg=true)](https://ci.appveyor.com/project/TristanSloughter/rebar3)
 
 1. [What is Rebar3?](#what-is-rebar3)
 2. [Why Rebar3?](#why-rebar3)
@@ -64,12 +64,12 @@ $ wget https://s3.amazonaws.com/rebar3/rebar3 && chmod +x rebar3
 From Source (assuming you have a full Erlang install):
 
 ```bash
-$ git clone https://github.com/rebar/rebar3.git
+$ git clone https://github.com/erlang/rebar3.git
 $ cd rebar3
 $ ./bootstrap
 ```
 
-Stable versions can be obtained from the [releases page](https://github.com/rebar/rebar3/releases).
+Stable versions can be obtained from the [releases page](https://github.com/erlang/rebar3/releases).
 
 The rebar3 escript can also extract itself with a run script under the user's home directory:
 
@@ -159,13 +159,13 @@ quick feedback, you can try the #rebar channel on
 asking about things with well known answers.
 
 For bug reports, roadmaps, and issues, visit the [github issues
-page](https://github.com/rebar/rebar3/issues).
+page](https://github.com/erlang/rebar3/issues).
 
 General rebar community resources and links:
 
 - [Rebar Mailing List](http://lists.basho.com/pipermail/rebar_lists.basho.com/)
 - #rebar on [irc.freenode.net](http://freenode.net/)
-- [issues](https://github.com/rebar/rebar3/issues)
+- [issues](https://github.com/erlang/rebar3/issues)
 - [Documentation](http://www.rebar3.org/v3.0/docs)
 
 To contribute to rebar3, please refer to [CONTRIBUTING](CONTRIBUTING.md).

src/rebar_prv_dialyzer.erl

@@ -97,7 +97,7 @@ do(State) ->
     end.
 
 %% This is used to workaround dialyzer quirk discussed here
-%% https://github.com/rebar/rebar3/pull/489#issuecomment-107953541
+%% https://github.com/erlang/rebar3/pull/489#issuecomment-107953541
 %% Dialyzer gets default plt location wrong way by peeking HOME environment
 %% variable which usually is not defined on Windows.
 maybe_fix_env() ->

src/rebar_prv_report.erl

@@ -13,7 +13,7 @@
 
 -define(PROVIDER, report).
 -define(DEPS, []).
--define(ISSUES_URL, "https://github.com/rebar/rebar3/issues").
+-define(ISSUES_URL, "https://github.com/erlang/rebar3/issues").
 
 %% ===================================================================
 %% Public API