This came up on the Fediverse: @[email protected] wanted to automatically add titles to the posts on his microblog.
This automation would have to be compatible with all the editors, including the mobile app.
Tag: Tutorial
GitHub’s API is really handy when you want to get stats about one of your repositories. Its GraphQL API in particular is really powerful. I’ve shown how it could be used to fetch project information in my GitHub Actions tutorial.
While working on another project, I ran into a limitation that had me scratch my head for quite a bit. I wanted to share my workaround for anyone who may run into this problem in the future.
A few months ago, I published The Power of a Conversational Code Review Culture. I talked about the importance of being generous with your code examples. Using GitHub’s built-in suggestions or posting diffs with the changes you have in mind go a long way towards helping the Pull Request’s author. It makes it easier for them to understand your suggestion, and include it in their code.
If you’re the reviewer and you already do this, kudos to you! Today I’d like to focus on the point of view of the Pull Request author.
Following yesterday’s post, I’d like to do a bit of a follow-up. Sometimes you “just” want to add a Mastodon icon to your site, linking to your Mastodon profile:
I have one just like that on my home page, alongside my other Social Media links.
In this post, I’ll cover 3 different ways to add such an icon to your site.
After dipping my toes into the Fediverse for the past few months, I wanted the Jetpack plugin to be there to help bloggers who wanted to interact more with the Fediverse on their sites.
Jetpack includes Sharing buttons that can be handy for your readers to quickly share your posts to their Social Network of choice ; adding a Mastodon button seemed like a no-brainer!
Let’s keep working on our GitHub Action! In the first parts of our series, we’ve discovered how to automatically add labels to an issue. Let’s explore some of the other things we can do with the Octokit client.
This post is part of the GitHub Actions: build your own JavaScript action series.
- Part 1: build the basics of our first action.
- Part 2: leverage issue forms to automate priority assignment on your issues.
- Part 3: automatically add PRs to specific columns on a GitHub Project board.
If you’re not following this blog yet, sign up here to get an email as soon as part 4 comes out:
In our last post, we built a JavaScript GitHub Action. That automation automatically adds an “Issue Triaged” label to all newly opened issues.
That’s great, but not necessarily very useful. In this second post, let’s look at an example of what we could do to make this a bit more useful!
If you work on GitHub, you’ll know GitHub Actions are powerful; they’re a great way to automate some of the tasks you regularly do in your repository.
GitHub introduced a marketplace where you can find actions for just about everything. This is a great way to get started with actions, see how useful they can be for your own projects.
In this series of posts, I’d like to go a bit further. We’ll be creating our own action to fit our exact needs. We’ll develop it within our existing repository, using JavaScript and GitHub’s own Actions Toolkit.
The Jetpack plugin comes with a number of blocks and editor extensions. One of those features extends the existing Media blocks, and adds an option to find and upload images from Google Photos or Pexels:
While this can be super useful when you use Google Photos or need to find free stock photos for your posts, you may sometimes prefer to only see the default “Media Library” option.
I’ve used image sharing software for the past 5 years: CloudApp, Cloudup, Droplr, I tried them all. Those apps are great to quickly share screenshots, annotated images, gifs, or even screencasts with users. Sometimes, an image is worth a thousand words. :)
When I switched to Linux for my February challenge, I set out to find a cross-platform alternative to all those services. Here is what I came up with.