community VS toolkit

Check out how to create your own or feel free to borrow from Community Discussions’ templates.

Although GitHub did not have a plan to support this option, but AzureDevops and GitLab already supported this. https://github.com/community/community/discussions/8940 You can manually do it for now

[4]: https://github.com/community/community/discussions/37117

I think it's not about missing commands, but missing destination (package repo of "generic" type). Very same issue posted here: https://github.com/community/community/discussions/38083

btw - I know this exists, but it seems like the posts are responded to much: https://github.com/community/community/discussions/categories/copilot

It appears that you're using IPv6 (your ping is returning IPv6 addresses). A quick search shows some github services may not support IPv6 but that's just a guess

Yeah, Vundle's (presumably temporary) removal caught me off guard today on a fresh install. This, in turn, has caused me to take a hard look at the Vim plugins I was using. Turns out I only needed one...which I wrote. So I'm now just storing that one in the horrible "vanilla" Vim plugin scheme and putting that in my dotfile management.

Just a good reminder that dependencies will always let you down. It's just a matter of time. Oh, and never turn your back on a big company.

Here's the tracking on this issue:

https://github.com/community/community/discussions/48173

GitHub: "The VundleVim organization has been flagged. Because of that, your organization is hidden from the public."

It's a relatively new beta feature for GitHub.

Here's the support discussion ticket for this:

https://github.com/community/community/discussions/48173

>The VundleVim organization has been flagged.

Different libraries (like actions/toolkit and microsoft/azure-pipelines-task-lib) with more accessible and easy-to-use APIs are available out-of-box

I used the libraries from actions/toolkit to create my action. It's more comfortable than when I did it with Docker. I looked at all the libraries, and most of all: actions/core, actions/exec and actions/github.

The Action is built using TypeScript and Node.js, popular choices for GitHub Actions due to their excellent support for asynchronous operations, a crucial requirement considering the multiple I/O operations involved. In the initial setup, I used the actions/toolkit package which provides useful utilities to streamline the creation of GitHub Actions. I picked @actions/core for basic functionalities such as inputs, outputs, and error handling, @actions/github to interact with GitHub's REST API, and @actions/exec to execute shell commands.

The package @actions/github provides a hydrated Octokit.js client. Octokit.js is the SDK of GitHub and contains several subpackages like @octokit/rest and @octokit/graphql to interact with the REST or GraphQL API.

The GitHub Action was implemented with TypeScript using the GitHub Actions Toolkit and the OpenAI Node.js Library. The Action is activated on new comments on issues and pull requests if they mention @AdaGPT. The relevant issue number is determined from the event payload. Then all existing comments for this issue are read. If the issue is a pull request, the git diff is also read.

Creating actions can be an overwhelming task, so to help you on your journey, here are two indispensable resources that can assist you in getting started; Actions Toolkit and Javascript action template. Still, this article will dive into how to create an action.

Please support something like "allow-failure" for a given job

More than 2 years of ignoring requests to add an important feature (allow-failure) to Github Actions (ref, ref. When not ignoring, completely misunderstanding the feature as if those building Github Actions are unfamiliar with core features of competing platforms.