github-script VS workflows

It's also possible to use output through the github-script action.

I wrote a custom script to parse PR comments as input commands to interface with Terraform CLI, returning the output as bot comments. Each step of the workflow relies on GitHub Actions, including actions/github-script to interact with GitHub's API (while brushing up on my JavaScript!).

You can generate what to annotate with a few lines of shell and then use gihub-script

Nice idea, worth mentioning other features:

* Reusable workflows (note: matrix strategy doesn't work here): https://docs.github.com/en/actions/using-workflows/reusing-w...

* Composite actions: https://docs.github.com/en/actions/creating-actions/creating...

* Script as action: https://github.com/actions/github-script

* Using GitHub Packages and artifacts: https://docs.github.com/en/actions/publishing-packages/about...

* Using docker-compose-like services that run alongside of the container: https://docs.github.com/en/actions/using-containerized-servi...

And many, many more :)

actions/github-script@v5

This workflow makes use of the awesome github-script that makes working with API's a breeze!

GitHub support hasn't been helpful so far. If you use Chrome on Linux, type xfce4-screenshooter or flameshot and grab a screenshot. Then navigate to any issue or PR, for example, https://github.com/actions/github-script/issues/187 and in the comment box at the bottom, type Ctrl-V. Either you'll see your image get uploaded or you won't. You don't need to save nor submit the comment.

Note at the end of the bash, and we are leveraging a curl command to talk directly to the GitHub API. This curl command is meant for simplicity. All of this could have been done using the octokit.rest.js library or better github-script.

In this post, I am going to focus on the API and actions/github-script. This action makes it easy to quickly write a script in your workflow that uses the GitHub API and includes the workflow run context.

My new github action follows a simple workflow: Whenever a user opens a pull request to the repository with the configured workflow, a comment is made on the PR with a greeting to the user and another comment with the statistics about the repository and PR are posted. Used the github-scripts (https://github.com/actions/github-script) action to get the API and context to write my own script in the workflow. It was a very fun exercise for me. Thankyou Dev Team for this cool contest!

Hi HN,

I’m Aloke, one of the co-creators of commands.dev (https://www.commands.dev/) and an engineer at Warp (https://www.warp.dev/).

Commands.dev is a curated, open-source collection of popular terminal commands that lets you quickly search for hard-to-remember terminal commands by title, tag, and description. Each of these pages are also indexed by Google to provide a consistent, well-formatted alternative to the variety of sources these commands turn up now, like StackOverflow.

As an engineer who uses the terminal frequently, I often have trouble remembering the exact command I want to execute if it’s not easily searchable within my terminal. Some commands that I run infrequently don’t match up with the underlying task they perform, which makes it even harder to find. For example, to undo my last git commit, I have to search for “git reset”, which I never remember because I’m always thinking “undo”ing my last commit instead of “reset”ing.

We built commands.dev so that there would be a centralized place to quickly find and search commands based on their name, description, or category. If you are a Warp user, these commands are also integrated directly into Warp as a feature we call Workflows (https://docs.warp.dev/features/workflows) so that you can quickly search and execute them directly from the terminal.

These commands are open-source (https://github.com/warpdotdev/workflows) and we would love contributions to make commands.dev even more useful. So far, we’ve already had 85 commands created by 22 unique contributors.

I’m excited to hear what you think of commands.dev! Our team sincerely hopes this will become a go-to tool on the Internet to consult when developers need to remember a difficult command, either directly on the site or by discovering a commands.dev page when searching Google for help with a command.

If you’re interested, join Warp’s Discord (www.warp.dev/discord) and follow us on Twitter (www.twitter.com/warpdotdev).

It's a good question, one that we are discussing a bunch.

We are planning to first open-source our Rust UI framework, and then parts and potentially all of our client codebase. The server portion of Warp will remain closed-source for now.

You can see how we’re thinking about open source here: https://github.com/warpdotdev/Warp/discussions/400 TLDR;

As a side note, we are open sourcing our extension points as we go. The community has already been contributing new themes [https://github.com/warpdotdev/themes]. And we’ve just opened a repository for the community to contribute common useful commands. [https://github.com/warpdotdev/workflows]