diff --git a/1_Set up job.txt b/1_Set up job.txt new file mode 100644 index 0000000..596622c --- /dev/null +++ b/1_Set up job.txt @@ -0,0 +1,33 @@ +2022-04-02T07:49:25.4902078Z Current runner version: '2.289.2' +2022-04-02T07:49:25.4928437Z ##[group]Operating System +2022-04-02T07:49:25.4928946Z Ubuntu +2022-04-02T07:49:25.4929242Z 20.04.4 +2022-04-02T07:49:25.4929530Z LTS +2022-04-02T07:49:25.4929778Z ##[endgroup] +2022-04-02T07:49:25.4930170Z ##[group]Virtual Environment +2022-04-02T07:49:25.4930551Z Environment: ubuntu-20.04 +2022-04-02T07:49:25.4930892Z Version: 20220227.1 +2022-04-02T07:49:25.4931373Z Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20220227.1/images/linux/Ubuntu2004-Readme.md +2022-04-02T07:49:25.4932062Z Image Release: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F20220227.1 +2022-04-02T07:49:25.4932559Z ##[endgroup] +2022-04-02T07:49:25.4932874Z ##[group]Virtual Environment Provisioner +2022-04-02T07:49:25.4933248Z 1.0.0.0-main-20220307-1 +2022-04-02T07:49:25.4933579Z ##[endgroup] +2022-04-02T07:49:25.4934527Z ##[group]GITHUB_TOKEN Permissions +2022-04-02T07:49:25.4935109Z Actions: write +2022-04-02T07:49:25.4935460Z Checks: write +2022-04-02T07:49:25.4936346Z Contents: write +2022-04-02T07:49:25.4936629Z Deployments: write +2022-04-02T07:49:25.4936964Z Discussions: write +2022-04-02T07:49:25.4937293Z Issues: write +2022-04-02T07:49:25.4937558Z Metadata: read +2022-04-02T07:49:25.4937907Z Packages: write +2022-04-02T07:49:25.4938223Z Pages: write +2022-04-02T07:49:25.4938500Z PullRequests: write +2022-04-02T07:49:25.4938865Z RepositoryProjects: write +2022-04-02T07:49:25.4939228Z SecurityEvents: write +2022-04-02T07:49:25.4939548Z Statuses: write +2022-04-02T07:49:25.4939864Z ##[endgroup] +2022-04-02T07:49:25.4943715Z Secret source: Actions +2022-04-02T07:49:25.4944182Z Prepare workflow directory +2022-04-02T07:49:25.5805493Z Prepare all required actions diff --git a/2_Send greeting.txt b/2_Send greeting.txt new file mode 100644 index 0000000..50f3fb8 --- /dev/null +++ b/2_Send greeting.txt @@ -0,0 +1,5 @@ +2022-04-02T07:49:25.7281031Z ##[group]Run echo "Hello World" +2022-04-02T07:49:25.7281526Z echo "Hello World" +2022-04-02T07:49:25.7773269Z shell: /usr/bin/bash -e {0} +2022-04-02T07:49:25.7773707Z ##[endgroup] +2022-04-02T07:49:25.8309689Z Hello World diff --git a/3_Complete job.txt b/3_Complete job.txt new file mode 100644 index 0000000..98defc6 --- /dev/null +++ b/3_Complete job.txt @@ -0,0 +1 @@ +2022-04-02T07:49:25.8549593Z Cleaning up orphan processes diff --git a/download.txt b/download.txt new file mode 100644 index 0000000..d7efd7d --- /dev/null +++ b/download.txt @@ -0,0 +1,278 @@ + + + + api – The GitHub Blog + + https://github.blog + Updates, ideas, and inspiration from GitHub to help developers build and design software. + Mon, 06 Jun 2022 20:48:59 +0000 + en-US + + hourly + + 1 + https://wordpress.org/?v=6.0 + + + https://github.blog/wp-content/uploads/2019/01/cropped-github-favicon-512.png?fit=32%2C32 + api – The GitHub Blog + https://github.blog + 32 + 32 + +153214340 + Custom repository roles are now GA + https://github.blog/changelog/2022-06-06-custom-repository-roles-are-now-ga + + + Mon, 06 Jun 2022 20:48:59 +0000 + https://github.blog/changelog/2022-06-06-custom-repository-roles-are-now-ga + + + Custom repository roles are now GA for GitHub.com and Enterprise Server 3.5.

+

Organization admins can create custom repository roles available to all repositories in their organization. Roles can be configured from a set of 35 fine grained permissions covering discussions, issues, pull requests, repos, and security alerts. Once a role is created, repository admins can assign a custom role to any individual or team in their repository.

+

Custom repository roles can be managed in the Repository roles tab of your Organization settings:

+

image

+

Custom repository roles are also supported in the GitHub REST APIs. The Custom Roles API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams support custom repository roles.

+

To get started with custom repository roles, read the docs.

+]]> + + + + 65509 + + Increased file size limit when retrieving file contents via REST API + https://github.blog/changelog/2022-05-03-increased-file-size-limit-when-retrieving-file-contents-via-rest-api + + + Tue, 03 May 2022 23:15:04 +0000 + https://github.blog/changelog/2022-05-03-increased-file-size-limit-when-retrieving-file-contents-via-rest-api + + + Previously, the Get repository content REST API endpoint had a file size limit of 1 MB. That didn’t correspond to the Create or update file contents endpoint which has a file size limit of 100 MB. Now, both endpoints have a file size limit of 100 MB. However, requests for file contents larger than 1 MB must include the .raw custom media type in the Accept HTTP header, as shown here:

+
+Accept: application/vnd.github.v3.raw
+
+

Read more about GitHub's REST API endpoints for repository contents.

+]]> + + + + 64749 + + Enable OAuth Device Authentication Flow for Apps + https://github.blog/changelog/2022-03-16-enable-oauth-device-authentication-flow-for-apps + + + Thu, 17 Mar 2022 04:40:59 +0000 + https://github.blog/changelog/2022-03-16-enable-oauth-device-authentication-flow-for-apps + + + From today the OAuth Device Authorization flow feature must be manually enabled for all OAuth and GitHub Apps. This change reduces the likelihood of Apps being used in phishing attacks against GitHub users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication.

+

If you own or manage an OAuth App or GitHub App that makes use of the OAuth Device Authorization flow, you can enable it for your App via its settings page:

+

Enable device flow

+

The OAuth Device Authorization flow API endpoints will respond with status code 400 to Apps that have not enabled this feature.

+

Learn more about the OAuth Device Authorization flow.

+]]> + + + + 63689 + + Paused: Sunset of Deprecated Teams API Endpoints + https://github.blog/changelog/2022-03-04-paused-sunset-of-deprecated-teams-api-endpoints + + + Fri, 04 Mar 2022 19:15:19 +0000 + https://github.blog/changelog/2022-03-04-paused-sunset-of-deprecated-teams-api-endpoints + + + We recently announced a plan to sunset deprecated Teams API endpoints over the coming weeks. On March 1, we conducted the first scheduled brownout for 12 hours.

+

As we gathered metrics and consumer feedback on the brownout, we formed a new understanding of its impact on our consumers and parallel work. Consequently, we are deciding to pause the remainder of the sunset. Instead, we will sunset deprecated Teams API endpoints over a new timeline in the coming months as we invest more deeply into API versioning and our Octokit SDKs.

+

If you are using a deprecated endpoint under a /teams/:team_id path, we continue to encourage you to switch to the /organizations/:org_id/team/:team_id path. Please refer to the REST API documentation to learn more about supported Teams API endpoints.

+]]> + + + + 63551 + + Opt in needed to keep OAuth Device Authorization Flow working + https://github.blog/changelog/2022-03-02-opt-in-needed-to-keep-oauth-device-authorization-flow-working + + + Wed, 02 Mar 2022 22:56:09 +0000 + https://github.blog/changelog/2022-03-02-opt-in-needed-to-keep-oauth-device-authorization-flow-working + + + On March 16 2022 the OAuth Device Authorization flow will become an "opt in" feature for all OAuth and GitHub Apps. This change reduces the likelihood of Apps being used in phishing attacks against GitHub users.

+

If you own or manage an OAuth App or GitHub App that makes use of the OAuth Device Authorization flow, you should enable it for your Apps via its settings page:

+

Enable device flow

+

The OAuth Device Authorization flow API endpoints will respond with status code 400 to Apps that have not opted in to this feature.

+

Learn more about the OAuth Device Authorization flow.

+]]> + + + + 63535 + + Sunset Notice: Deprecated Teams API Endpoints + https://github.blog/changelog/2022-02-22-sunset-notice-deprecated-teams-api-endpoints + + + Tue, 22 Feb 2022 22:00:25 +0000 + https://github.blog/changelog/2022-02-22-sunset-notice-deprecated-teams-api-endpoints + + + Update on March 4, 2022: We have temporarily paused the sunset. Please read the official announcement for more information.

+
+

In early 2020, we moved the Teams API from a top-level path under /teams/:team_id to a scoped path under the organization that owns the team like /organizations/:org_id/team/:team_id and added support to make the API available under a named path like /orgs/:org/teams/:team_slug.

+

Over the next few weeks, we will be sunsetting the API endpoints under /teams/:team_id.

+

Timeline

+

Brownouts

+
    +
  • March 1, 2022 for 12 hours starting at 14:00 UTC
    • +
  • March 8, 2022 for 24 hours starting at 14:00 UTC
    • +
+

If you make a request to an affected endpoint during the brownouts, GitHub will respond with a client error.

+

Removal

+
    +
  • March 15, 2022 at 14:00 UTC
    • +
+

Affected endpoints

+
    +
  • GET /teams/:team_id
    • +
  • PATCH /teams/:team_id
    • +
  • DELETE /teams/:team_id
    • +
  • GET /teams/:team_id/teams
    • +
  • GET /teams/:team_id/repos
    • +
  • GET /teams/:team_id/repos/:owner/:repo
    • +
  • PUT /teams/:team_id/repos/:owner/:repo
    • +
  • DELETE /teams/:team_id/repos/:owner/:repo
    • +
  • GET /teams/:team_id/projects
    • +
  • GET /teams/:team_id/projects/:project_id
    • +
  • PUT /teams/:team_id/projects/:project_id
    • +
  • DELETE /teams/:team_id/projects/:project_id
    • +
  • GET /teams/:team_id/members
    • +
  • GET /teams/:team_id/members/:username
    • +
  • PUT /teams/:team_id/members/:username
    • +
  • DELETE /teams/:team_id/members/:username
    • +
  • GET /teams/:team_id/memberships/:username
    • +
  • PUT /teams/:team_id/memberships/:username
    • +
  • DELETE /teams/:team_id/memberships/:username
    • +
  • GET /teams/:team_id/invitations
    • +
+

Steps to take

+

The easiest way to update your code is to switch to the /organizations/:org_id/team/:team_id path. If you're unsure of what org_id to use, you can GET the current team under /teams/:team_id and find the id field inside the organization hash in the response.

+

Please refer to the REST API documentation to learn more about supported Teams API endpoints.

+]]> + + + + 63440 + + Dependabot alerts: access state, fixed alerts, and numeric identifier via GraphQL API + https://github.blog/changelog/2022-02-15-dependabot-alerts-access-state-fixed-alerts-and-numeric-identifier-via-graphql-api + + + Wed, 16 Feb 2022 00:45:33 +0000 + https://github.blog/changelog/2022-02-15-dependabot-alerts-access-state-fixed-alerts-and-numeric-identifier-via-graphql-api + + + This release adds support for viewing fixed alerts to the GraphQL API. This update also adds the ability to access and filter by state, as well as access unique numeric identifier.

+

The additions include these new fields to a RepositoryVulnerabilityAlert:

+
    +
  • number
    • +
  • fixed_at
    • +
  • fix_reason
    • +
  • state
    • +
+

And we're adding the ability to filter by state on the vulnerability alert object.

+

For more information, see Dependabot alerts in the GraphQL API reference.

+]]> + + + + 63292 + + Legacy Delete reactions REST API removed + https://github.blog/changelog/2022-02-11-legacy-delete-reactions-rest-api-removed + + + Fri, 11 Feb 2022 16:16:45 +0000 + https://github.blog/changelog/2022-02-11-legacy-delete-reactions-rest-api-removed + + + In February 2020 we announced the deprecation of the general purpose "Delete reactions" REST API in favor of separate REST APIs for each place reactions can be applied. The old endpoint has been removed, which sets us up to scale and support the Reactions API better in the long run.

+

Learn more about the supported REST APIs for deleting reactions for issues, pull request comments, and more.

+]]> + + + + 63047 + + Code scanning organization-level REST API + https://github.blog/changelog/2022-02-07-code-scanning-organization-level-rest-api + + + Mon, 07 Feb 2022 17:39:57 +0000 + https://github.blog/changelog/2022-02-07-code-scanning-organization-level-rest-api + + + Users can now retrieve all their code scanning alerts at the GitHub organization level via the REST API. This new API endpoint supplements the existing repository level endpoint.

+

This API is available on GitHub.com starting today and will also be available to GitHub Enterprise Server users starting version 3.5.

+

Learn more about the code scanning REST API
+Learn more about GitHub Advanced Security

+]]> + + + + 62897 + + GitHub’s SSH host keys are now published in the API + https://github.blog/changelog/2022-01-18-githubs-ssh-host-keys-are-now-published-in-the-api + + + Tue, 18 Jan 2022 16:39:58 +0000 + https://github.blog/changelog/2022-01-18-githubs-ssh-host-keys-are-now-published-in-the-api + + + The GitHub metadata endpoint now contains our SSH host keys.
+(We'll continue offering host key fingerprints as well.)

+
{
+  // new entry
+  "ssh_keys": [
+    "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl",
+    "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg=",
+    "ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ=="
+  ],
+  // existing entry
+  "ssh_key_fingerprints": [
+    "SHA256_RSA": "nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8",
+    "SHA256_ECDSA": "p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM",
+    "SHA256_ED25519": "+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU"
+  ],
+  // ... rest of payload
+}
+

These keys are in the OpenSSH known_hosts format for easy inclusion into existing known_hosts files.
+This will make it easier to preconfigure systems which expect to connect via SSH.
+For example, you can prime your CI runners with these keys before starting to fetch from GitHub.

+

The keys returned from the API include both SSH host keys that we're actively using, plus any that we're advertising via host key rotation for future use.
+Currently, we're not offering any keys via rotation that aren't actively in use, but if we announce new host keys in the future, you can find them here as well during the rotation period.

+

See the meta API endpoint to learn more.

+]]> + + + + 62466 + +