Merge pull request #864 from hzeller/change-urls

Fix URLs to point to the changed github repository.
chipsalliance · Jul 8, 2021 · 27add07 · 27add07
2 parents fce34d2 + 4c5e2c7
commit 27add07
Show file tree

Hide file tree

Showing 11 changed files with 23 additions and 22 deletions.
diff --git a/.github/bin/build-and-test.sh b/.github/bin/build-and-test.sh
@@ -43,7 +43,7 @@ BAZEL_OPTS="${BAZEL_OPTS} --cxxopt=-Wno-array-bounds"
 # Warnings that come from other external parts that we compile.
 # Ideally, we would separate them out to ignore only there, while we keep
 # tight warnings on for 'our' code-base.
-# TODO(hzeller): Remove after https://github.com/google/verible/issues/747
+# TODO(hzeller): Remove after https://github.com/chipsalliance/verible/issues/747
 #                is figure out
 BAZEL_OPTS="${BAZEL_OPTS} --cxxopt=-Wno-cast-function-type"       # gflags
 BAZEL_OPTS="${BAZEL_OPTS} --cxxopt=-Wno-deprecated-declarations"  # jsconcpp

diff --git a/.github/bin/run-clang-format.sh b/.github/bin/run-clang-format.sh
@@ -22,7 +22,7 @@ find . -name "*.h" -o -name "*.cc" | xargs -P2 clang-format --style=Google -i
 git diff > ${FORMAT_OUT}
 
 if [ -s ${FORMAT_OUT} ]; then
-   echo "Style not matching (see https://github.com/google/verible/blob/master/CONTRIBUTING.md#style)"
+   echo "Style not matching (see https://github.com/chipsalliance/verible/blob/master/CONTRIBUTING.md#style)"
    echo "On your *.h, *.cc files, please run clang-format -i --style=file <your changed files>"
    cat ${FORMAT_OUT}
    exit 1

diff --git a/.github/bin/run-kythe.sh b/.github/bin/run-kythe.sh
@@ -32,7 +32,7 @@ then
   bazel \
     build \
     --experimental_action_listener=":extract_cxx" \
-    --define="kythe_corpus=github.com/google/verible" \
+    --define="kythe_corpus=github.com/chipsalliance/verible" \
     -- \
     //...
 else
@@ -42,7 +42,7 @@ else
     --bazelrc="${KYTHE_DIR_ABS}/extractors.bazelrc" \
     build \
     --override_repository kythe_release="${KYTHE_DIR_ABS}" \
-    --define="kythe_corpus=github.com/google/verible" \
+    --define="kythe_corpus=github.com/chipsalliance/verible" \
     -- \
     //...
 fi

diff --git a/README.md b/README.md
@@ -1,7 +1,7 @@
 # Verible
 
 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
-[![Continuous Integration](https://github.com/google/verible/workflows/verible-ci/badge.svg)](https://github.com/google/verible/actions/workflows/verible-ci.yml)
+[![Continuous Integration](https://github.com/chipsalliance/verible/workflows/verible-ci/badge.svg)](https://github.com/chipsalliance/verible/actions/workflows/verible-ci.yml)
 
 <!--*
 freshness: { owner: 'hzeller' reviewed: '2020-10-08' }
@@ -138,7 +138,7 @@ Features (various degress of work-in-progress):
 
 <!--
 TODO(fangism): a demo GIF animation here.
-See https://github.com/google/verible/issues/528
+See https://github.com/chipsalliance/verible/issues/528
 -->
 
 ### Lexical Diff
@@ -163,7 +163,7 @@ potentially sensitive test cases with tool vendors.
 
 <!--
 TODO(fangism): a short demo GIF animation here.
-See https://github.com/google/verible/issues/528
+See https://github.com/chipsalliance/verible/issues/528
 -->
 
 ### Preprocessor
@@ -195,4 +195,4 @@ abstract syntax tree (AST). If you are interested in collaborating, contact us.
 [lint-rule-list_enum-name-style]: https://google.github.io/verible/lint.html#enum-name-style
 [lint-rule-list_line-length]: https://google.github.io/verible/lint.html#line-length
 [lint-rule-list_no-tabs]: https://google.github.io/verible/lint.html#no-tabs
-[binary releases]: https://github.com/google/verible/releases
+[binary releases]: https://github.com/chipsalliance/verible/releases
diff --git a/doc/development.md b/doc/development.md
@@ -6,7 +6,7 @@ Verible. Collecting development aids and design concepts.
 ## Searching and Navigating Verible's Source Code
 
 https://cs.opensource.google/verible/verible is a search-indexed mirror of
-[Verible's source code](https://github.com/google/verible). Expect to spend a
+[Verible's source code](https://github.com/chipsalliance/verible). Expect to spend a
 lot of time here as you familiarize yourself with the codebase.
 
 https://developers.google.com/code-search/reference provides a reference for

diff --git a/doc/style_lint.md b/doc/style_lint.md
@@ -16,9 +16,9 @@ Before you begin, familiarize yourself with:
 *   Join the developer's mailing list: [email protected]
     ([join](https://groups.google.com/forum/#!forum/verible-dev/join))
 *   Use the github issue tracker, discuss and comment:
-    *   [existing lint rule issues](https://github.com/google/verible/issues?q=is%3Aissue+is%3Aopen+label%3Astyle-linter)
-    *   [file new issue about existing rule](https://github.com/google/verible/issues/new?assignees=&labels=style-linter&template=style-linter-bug.md&title=)
-    *   [file new issue about a new rule](https://github.com/google/verible/issues/new?assignees=&labels=enhancement%2C+style-linter&template=style-linter-feature-request.md&title=)
+    *   [existing lint rule issues](https://github.com/chipsalliance/verible/issues?q=is%3Aissue+is%3Aopen+label%3Astyle-linter)
+    *   [file new issue about existing rule](https://github.com/chipsalliance/verible/issues/new?assignees=&labels=style-linter&template=style-linter-bug.md&title=)
+    *   [file new issue about a new rule](https://github.com/chipsalliance/verible/issues/new?assignees=&labels=enhancement%2C+style-linter&template=style-linter-feature-request.md&title=)
 
 ## Whose Style Guide?
 

diff --git a/verilog/CST/README.md b/verilog/CST/README.md
@@ -49,17 +49,17 @@ _Ideal_ properties of CST nodes:
 
 This is not the case today because of the haste in which initial development
 took place, but help is wanted towards achieving the aforementioned ideals. See
-also https://github.com/google/verible/issues/159.
+also https://github.com/chipsalliance/verible/issues/159.
 
 ## Abstract Syntax Tree?
 
 _Wouldn't an abstract syntax tree (AST) satisfy the above ideals?_ Yes, this
 would take time to write, and we would need
-[help](https://github.com/google/verible/issues/184).
+[help](https://github.com/chipsalliance/verible/issues/184).
 
 An AST may not be a great representation for _unpreprocessed_ code, which is the
 focus of the first developer tool applications. Having a
-[standard-compliant SV preprocessor](https://github.com/google/verible/issues/183)
+[standard-compliant SV preprocessor](https://github.com/chipsalliance/verible/issues/183)
 would pave the way to making an AST more useful.
 
 ## Testing

diff --git a/verilog/CST/declaration.cc b/verilog/CST/declaration.cc
@@ -147,7 +147,7 @@ GetUnqualifiedIdFromVariableDeclarationAssignment(
     // This is a workaround for the below:
     // TODO(fangism): remove this condition after fixing the issue for "branch".
     // "riscv_instr          branch;"
-    // issue on github: https://github.com/google/verible/issues/547
+    // issue on github: https://github.com/chipsalliance/verible/issues/547
     return verible::SymbolCastToLeaf(*identifier);
   }
   return *AutoUnwrapIdentifier(*identifier);

diff --git a/verilog/CST/type.cc b/verilog/CST/type.cc
@@ -320,7 +320,7 @@ const verible::SyntaxTreeNode* GetTypeIdentifierFromDataType(
   //   x = 1;
   // This is the whole test case.
   // This is a global, implicit-type data declaration, initialized.
-  // See https://github.com/google/verible/issues/549
+  // See https://github.com/chipsalliance/verible/issues/549
   if (data_type_node.children().empty()) {
     return nullptr;
   }

diff --git a/verilog/analysis/verilog_project.h b/verilog/analysis/verilog_project.h
@@ -74,7 +74,7 @@ class VerilogSourceFile {
   absl::string_view ReferencedPath() const { return referenced_path_; }
 
   // Returns the corpus to which this file belongs (e.g.,
-  // github.com/google/verible).
+  // github.com/chipsalliance/verible).
   absl::string_view Corpus() const { return corpus_; }
 
   // Returns a (possibly more qualified) path to the file.
@@ -130,7 +130,8 @@ class VerilogSourceFile {
   // such so this class can have a default move constructor.
   std::string resolved_path_;
 
-  // The corpus to which this file belongs to (e.g., github.com/google/verible).
+  // The corpus to which this file belongs to (e.g.,
+  // github.com/chipsalliance/verible).
   absl::string_view corpus_;
 
   // State of this file.
@@ -293,7 +294,7 @@ class VerilogProject {
   const std::vector<std::string> include_paths_;
 
   // The corpus to which this project belongs (e.g.,
-  // 'github.com/google/verible').
+  // 'github.com/chipsalliance/verible').
   const std::string corpus_;
 
   // Set of opened files, keyed by referenced (not resolved) filename.

diff --git a/verilog/preprocessor/README.md b/verilog/preprocessor/README.md
@@ -21,12 +21,12 @@ the limitations of preprocessing support in the parser, which in turn improves
 the outreach of tools like the linter and formatter.
 
 Most of these are not yet implemented, but
-[help is wanted](https://github.com/google/verible/issues/183).
+[help is wanted](https://github.com/chipsalliance/verible/issues/183).
 
 ## Standard-Compliant SV Preprocessor
 
 ... does not exist in this codebase yet. See
-https://github.com/google/verible/issues/183.
+https://github.com/chipsalliance/verible/issues/183.
 
 SystemVerilog preprocessing is in many ways
 [more complicated than C/C++ preprocessing](https://www.veripool.org/papers/Preproc_Good_Evil_SNUGBos10_paper.pdf).