diff --git a/content/actions/guides/building-and-testing-ruby.md b/content/actions/guides/building-and-testing-ruby.md index e2862acd67..03c85c0a50 100644 --- a/content/actions/guides/building-and-testing-ruby.md +++ b/content/actions/guides/building-and-testing-ruby.md @@ -49,10 +49,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: 2.6 - name: Install dependencies @@ -66,7 +63,7 @@ jobs: The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby). -Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. +Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby. The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner. @@ -122,10 +119,7 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Ruby ${{ matrix.ruby-version }} - # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby, - # change this to (see https://github.com/ruby/setup-ruby#versioning): - # uses: ruby/setup-ruby@v1 - uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0 + uses: ruby/setup-ruby@v1 with: ruby-version: ${{ matrix.ruby-version }} - name: Install dependencies diff --git a/content/github/site-policy/github-subprocessors-and-cookies.md b/content/github/site-policy/github-subprocessors-and-cookies.md index fb4b630555..fcb3e91945 100644 --- a/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,7 +10,7 @@ versions: free-pro-team: '*' --- -Effective date: **January 21, 2021** +Effective date: **January 29, 2021** GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -27,7 +27,6 @@ When we share your information with third party subprocessors, such as our vendo | Discourse | Community forum software provider | United States | United States | | Eloqua | Marketing campaign automation | United States | United States | | Google Apps | Internal company infrastructure | United States | United States | -| Google Analytics | Analytics and performance | United States | United States | | MailChimp | Customer ticketing mail services provider | United States | United States | | Mailgun | Transactional mail services provider | United States | United States | | Microsoft | Microsoft Services | United States | United States | diff --git a/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index 15918305b3..f045697c83 100644 --- a/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -199,7 +199,14 @@ If we receive a request for information under certain exigent circumstances (whe ### Cost reimbursement -We reserve the right to seek reimbursement for administrative costs associated with responding to requests for information, as allowed by law. +Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders. + +While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law: + +- Initial search of up to 25 identifiers: Free +- Production of subscriber information/data for up to 5 accounts: Free +- Production of subscriber information/data for more than 5 accounts: $20 per account +- Secondary searches: $10 per search ### Data preservation @@ -215,14 +222,6 @@ c/o Corporation Service Company 2710 Gateway Oaks Drive, Suite 150N Sacramento, CA 95833-3505 ``` -Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders. - -While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law: - -- Initial search of up to 25 identifiers: Free -- Production of subscriber information/data for up to 5 accounts: Free -- Production of subscriber information/data for more than 5 accounts: $20 per account -- Secondary searches: $10 per search Please make your requests as specific and narrow as possible, including the following information: