
If you want to prevent bots like ChatGPT from scraping and parsing a website, the robots.txt file is the one to update.

This is the file usually used to tell search engines which pages to index and which ones to ignore. In this case, you can use it to block AI bots or in that case, specifically ChatGPT. The only caveat is that it can't remove pages that have already been indexted.

Simply add the following line in your `robots.txt` file:

```
User-agent: GPTBot
Disallow: /
```

This code snippet will tell ChatGPT that it is not allowed to access any part or page of the site.

Whatever ChatGPT and Open AI actually respect this standard is up to them, but it's a good start. Of course, it may not be enough to prevent unwanted scraping and parsing and you may want to put in place additional measures such as implementing CAPTCHAs, using a content security policy, etc...

## References

- [GPTBot](https://platform.openai.com/docs/gptbot)


How to block ChatGPT from scraping and parsing your website? It may be simpler than you think.

How To Block ChatGPT form Scraping and Parsing your Website?


I have seen way too many times people using the `<hr>` HTML element, which is called "thematic break" instead of CSS.

Using the HTML `<hr>` tag purely for designing horizontal lines is an incorrect practice.
The real purpose of the `<hr>` tag is to denote a thematic break in the content (like between paragraphs), not just to visually create a horizontal rule.

If you need a decorative line, CSS is a more appropriate choice.

For instance:

```html
<div class="styled-line">Some content</div>
```

Example CSS:

```css
.styled-line {
  border-bottom: 1px solid #000;
  margin: 1em 0;
}
```

You generally don't want to have a single empty `<span>` or `<div>` element just to style it as a horizontal line. Often times, you can just use a bottom border on the element above it.

In terms of accessibility, using `<hr>` as a design element can confuse screen reader users, as it indicates a "thematic break".

Semantics are important, not only for accessibility but also for SEO. So, please, stop using the `<hr>` tag to design a horizontal line!


It's sometimes easy to forget that UI doesn't dicated semantics. In this article I'll show you how to use the "<hr/>" tag properly.

Stop using the "<hr/>" tag to design a horizontal line!


You may be getting the issue **"The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files."** from your Github workflow.

![Screenshot showing the 'set-output' issue from the Github workflows](/images/notes/set-output-nvmrc-github-actions.jpg)

Few months ago, I choose to update some of my Github workflows to read from my `.nvmrc` file instead of manually specifying my node version.

```.bash:.github/workflows/production.yml
on: push

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - name: Detect Node version
        run: echo ::set-output name=NODE_VERSION::$(cat .nvmrc)
        id: nvmrc

      - name: Use Node.js ${{ steps.nvmrc.outputs.NODE_VERSION }}
        uses: actions/setup-node@v3
        with:
          node-version: ${{ steps.nvmrc.outputs.NODE_VERSION }}
```

But [since October 2022](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/) and the runner version `2.298.2`, Github shows a warning regarding a future depreciation of the `set-output` command.

After few trials, I figured out how to update using the `$GITHUB_OUTPUT` instead:

```.bash:.github/workflows/update-production.yml
on: push

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - name: Detect Node version
        run: echo "NODE_VERSION=$(cat .nvmrc)" >> $GITHUB_OUTPUT
        id: nvmrc
        # shell: bash (to be added if you use composite actions)

      - name: Use Node.js ${{ steps.nvmrc.outputs.NODE_VERSION }}
        uses: actions/setup-node@v3
        with:
          node-version: '${{ steps.nvmrc.outputs.NODE_VERSION }}'
```

And "voilà", the warning should have disappeared and you should see the number of the version right after `Use Node.js XXXX` in your workflow.


Find out how to fix the deprecated set-output when you read the Nodejs version from your .nvmrc file in Github workflows.

How to fix "set-output" when reading nvmrc from the GitHub Actions?


When recently working on my blog, I tried to add a `postbuild` scripts with `next-sitemap` in my `package.json`. My goal was to automatically generate `.xml` files after each Next.js builds.

Using [pnpm](https://pnpm.io/), I found out that my `postbuild` was working with `npm` but not `pnpm`.

I found out [this issue](https://github.com/pnpm/pnpm/issues/2891) on Github mentionning the same problem I encountered. It seems that pre/posts scripts are not activated if using pnpm.

I found the solution adding the line below in my `.npmrc` local file:

```.bash:.npmrc
enable-pre-post-scripts=true
```

Now I can use pre/posts scripts and `pnpm`. I hope this could save you some time!


Find out what I had to update to use pre and posts scripts with pnpm.

Tag: coding

How To Block ChatGPT form Scraping and Parsing your Website?

Stop using the "<hr/>" tag to design a horizontal line!

How to fix "set-output" when reading nvmrc from the GitHub Actions?

How to fix "postbuild" and "prebuild" not working with pnpm?

Posts associated with coding

How To Block ChatGPT form Scraping and Parsing your Website?

Stop using the "<hr/>" tag to design a horizontal line!

How to fix "set-output" when reading nvmrc from the GitHub Actions?

How to fix "postbuild" and "prebuild" not working with pnpm?