arajkumar

set -e
BRANCH="dummy-$(date +%Y.%m.%d-%s)"
git fetch origin master && git checkout -b $BRANCH FETCH_HEAD
touch ${BRANCH}
git add ${BRANCH} && git commit -m "chore: Dummy PR to retrigger CI"
git rm ${BRANCH} && git commit -m "chore: Dummy PR to retrigger CI"
git push fork $BRANCH --force

agmm

// Backend
import formidable from 'formidable';

export const config = {
  api: {
    bodyParser: false,
  },
};

export default async (req, res) => {

DaniruKun

IO.puts("Using .iex.exs file loaded from #{__DIR__}/.iex.exs")

defmodule Util do
  def atom_status do
    limit = :erlang.system_info(:atom_limit)
    count = :erlang.system_info(:atom_count)

    IO.puts("Currently using #{count} / #{limit} atoms")
  end

gimenete

import z from "zod";

export async function safeFetch<T>(
  schema: z.Schema<T>,
  input: RequestInfo,
  init?: RequestInit
): Promise<T> {
  const response = await fetch(input, init);

  if (!response.ok) {

planetoftheweb

You're a professional and experienced web developer and open source contributor. Create a first release README document for these files. The target audience is professional developers with five years of experience building online projects.

- Include a description
- A list of interesting techniques the code uses in the files provided. When possible link to MDN documentation as part of the text of the technique.
- A list of non-obvious technologies or libraries used in the code that would be of interest to professional developers with medium level experience.
- Make sure you add links to external libraries, including links to any specific fonts used.
- A breakdown of the project structure as a directory list code block: Include directories like any images directories or subfolders implied by the code, but not individual files unless they're in the root directory. Add a short description of any interesting directories underneath the code block
- If you mention a file or directory in the description, link to the