Article Web-page to Markdown action

Language: English | 简体中文

Introduction

Automatically generate Markdown files based on the Web-pages of articles.

Project structure

news-translate
|  action.yml  // Entry file
│  package.json
│  README.md
│
|-.github
│  |-ISSUE_TEMPLATE
│  │   AutoGenerateMarkdown.md  // Automatically generate Markdown issue template
│  │
│  |-workflows
│      WebPageToMarkdown.yml  // Actions file for automatically generating Markdown files
│
|-dist  // Compiled static folder
│
|-node_modules
│
|-src
|  |-index.ts  // Entry file of the script
|  |-toMarkdownConstant.ts  // Configuration file
|  |-utilities.ts  // Function library file
|
|-test
   |-utilities.test.ts  // test file

Usage

Add the following step in the jobs field of your GitHub action configuration:

- uses: freeCodeCamp-China/article-webpage-to-markdown-action@v1
  with:
    newsLink: '${{ github.event.issue.Body }}'
    markDownFilePath: './articles/'
    githubToken: ${{ github.token }}

The following is an extended example with all possible options available for this Action:

- uses: freeCodeCamp-China/article-webpage-to-markdown-action@v1
  with:
    # A string contains an Original Article URL
    newsLink: '${{ github.event.issue.Body }}'
    # CSS selector of elements which should be ignored
    ignoreSelector: '.ad-wrapper'
    # Path of the generated MarkDown file
    # Relative path relative to current working directory
    markDownFilePath: './articles/'
    githubToken: ${{ github.token }}

Other Action get Markdown file path:

- name: fetch webpage to Markdown file
  # you need set action id
  id:  fetch-webpage-to-markdown
  uses: freeCodeCamp-China/article-webpage-to-markdown-action@v1
  with:
    # A string contains an Original Article URL
    newsLink: '${{ github.event.issue.Body }}'
    # CSS selector of elements which should be ignored
    ignoreSelector: '.ad-wrapper'
    # Path of the generated MarkDown file
    # Relative path relative to current working directory
    markDownFilePath: './articles/'
    githubToken: ${{ github.token }}

- name: Use the output from my custom action
  run: |
      markdown_file_path=${{ steps.fetch-webpage-to-markdown.outputs.markdown_file_path }}
      echo "The file path is ${{markdown_file_path}}"

If you do not configure the option markDownFilePath, the file is generated in the current path by default.

Run the script by the issue of GitHub

Issues >> New issue >> Fill in the title and description of the issue >> Submit new issue

Description

[Original article](https://example.com/path/to/your/article/)

Replace the Link Value with the URL of an Original article, after the issue submitted, the action will run, and a success or failed message will be commented to the issue in the end.

If the script execution fails, you need to confirm the problem, solve them, and post a new issue according to the previous steps. In the Action log, The Common Error Messages will give you some reliable tips.

Common Error Messages

• No parameters were found. Please confirm that the description of the issue has been entered. The description of the issue is empty, please fill in the content according to the template.
• There is one file with the same name exists. Please check if the article has been added. There is a file with the same name under the folder markDownFilePath.
• The DOM of the website has been modified, or there is a problem with loading, please confirm. The DOM structure of the website may be changed and the script needs to be modified.

---

Advanced cases

Client-side rendering

This action can only handle Static or Server-side rendered pages, for Client-side rendered pages, we recommend https://github.com/TechQuery/Web-fetch#in-github-actions .

---

Contributing guide

Please go to the contributing guide.

---

License

The computer software is licensed under the BSD-3-Clause license.