Awesome-Repo-Template

<a href="https://github.com/MarketingPipeline/Awesome-Repo-Template/"> <img height=350 alt="Repo Banner - Awesome Repo Template" src="https://capsule-render.vercel.app/api?type=waving&color=c4a2bd&height=300&section=header&text=Awesome%20Repo%-Template&fontSize=70&fontColor=ffffff&animation=fadeIn&fontAlignY=38&desc=Easily%20setup%20your%20next%20repo!&descAlignY=60&descAlign=50"></img></a> <p align="center"> <b>A awesome repo template to kick-start your next project</b> <br> <small> <b><i>Show your support!</i> </b></small> <br> <a href="https://github.com/MarketingPipeline/Awesome-Repo-Template"> <img title="Star on GitHub" src="https://img.shields.io/github/stars/MarketingPipeline/Awesome-Repo-Template.svg?style=social&label=Star"> </a> <a href="https://github.com/MarketingPipeline/Awesome-Repo-Template/fork"> <img title="Fork on GitHub" src="https://img.shields.io/github/forks/MarketingPipeline/Awesome-Repo-Template.svg?style=social&label=Fork"> </a> </p>

Features:

• A configurable workflow action to:
  • update all links with your own with EASE!
  • update Code Of Conduct E-mail with your own!
  • update Security Policy E-mail with your own!
  • download files & folder from another GitHub Repo
  • compress / optimize all images in repo!
  • generate a Markdown styled index file with SEO details!
  • generate a table of contents in your README
  • generate a star-gazer metrics SVG image
• Time Saving Files:
  • Pull request template
  • Issue templates for bug reports and
    feature requests
  • Contributor guidelines
  • Code Owners
  • Code of Conduct
  • Change-log
  • To-Do list
  • Security Policy
  • README
  • License file
  • GitHub Bot Files
    • config.yml file to modify multiple bot's behaviours.
    • issue_label_bot.yaml file to use the issue adder GitHub bot. Activate it or check its documentation.
    • settings.yml file to use the popular settings GitHub bot. Activate it or check its documentation.

Example and Usage

<br> <details><summary>How to use this <b>template</b>:</summary> <br>

To run any of these tasks you MUST be in the <b>Actions section</b>

<details><summary>How to find the <a href="https://github.com/MarketingPipeline/Awesome-Repo-Template/actions"><b>Action</b></a></summary>

<a href="https://github.com/MarketingPipeline/Awesome-Repo-Template/actions"> </a>

</details> <br> <br> <details><summary>How to replace all <b>links</b> with your own:</summary> <br>

Edit the repo_config.json file & set the value for "REPLACE_TEXT_WITH" - to your username & repo name like the following example

   MyUserName/My-Repo-Name

And run the Repo Generator in Actions - set "Update all links" to <code>checked</code>
<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <br> <details><summary>How to replace <b>e-mail</b> in <a href="CODE_OF_CONDUCT.md">Code of Conduct</a> with your own:</summary> <br>

Edit the repo_config.json file & set the value for "EMAIL" - to your e-mail address like the following example.

   hello_world@github.com

And run the Repo Generator in Actions- set "Update Code Of Conduct Info" to <code>checked</code>
<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <br> <details><summary>How to replace <b>e-mail</b> in <a href=".github/SECURITY.md">Security Policy</a> with your own:</summary> <br>

Edit the repo_config.json file & set the value for "EMAIL" - to your e-mail address like the following example.

   hello_world@github.com

And run the Repo Generator in Actions- set "Update Security Info" to <code>checked</code>
<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <br> <details><summary>How to <b>download</b> file(s) / folder(s) from another GitHub repo</summary> <br> <br> <h3> WARNING</h3> files downloaded from a repo containing the same name in your current repo will be OVER-WRITTEN. <br> <br> <br> <br>

In the Repo Generator Actions- set "Download a file or folder from a GitHub Repo" to a GitHub file path or folder.

Example(s)

To download a <b>single file</b>:

 https://github.com/Repo-Owner-UserName/Repo-Name/blob/master/README.md

To download a specific <b>folder</b>:

 https://github.com/Repo-Owner-UserName/Repo-Name/blob/master/Folder-Name
 

To download all files in a repo <b>folder</b>:

 https://github.com/Repo-Owner-UserName/Repo-Name/blob/master/
 
 

Note: File's will be placed into main repo path.

<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <br> <details><summary>How to generate a <b>index.html</b> file</summary> <br>

A index.html file will be produced from your README content.

SEO details such as Title, Description & OG images etc are auto-produced using your Repo details.

<b>Note</b> Your README content will be rendered in Github Flavored Markdown using our tool Markdown-Tag: Add Markdown to any HTML using a <md> tag

Go to the Repo Generator in Actions- set "Generate Index File" to <code>checked</code>
<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <br> <details><summary>How to <b>compress / optimize</b> images in repo</summary> <br>

<b><i>Note:</b></i> All images in repo will be compressed / optimized (SVG's are NOT supported)

Go to the Repo Generator in Actions- set "Compress / Optimize Images" to <code>checked</code>
<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <br> <br> <details><summary>How to generate <b>Table Of Contents</b>:</summary> <br> To generate tables of contents automatically use anywhere in your README.md file a comment like so

<!-- toc -->

<!-- tocstop -->

And when running the Repo Generator in Actions - set "Generate Table Of Contents" to <code>checked</code>

<b><i>WARNING:</i></b> Only 1 table of contents can be generated in a README - if you use more than one you WILL face problems.
<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <br> <br> <details><summary>How to Generate a <b>Metrics Image</b>:</summary> <br>

Create a Personal Access Token & create a repo secret called "METRICS_TOKEN" & when running the Repo Generator - set "Generate Metrics Image File" to <code>checked</code>

You will have an image generated that looks like this!

<img src="stargazers-metrics.svg"></img>

It will be placed in the main repo under the filename <code>stargazers-metrics.svg</code>

<i>Note:</i> if someone knows how to change this please make a pull request with the image placed to .github folder!

<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details>

<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <details><summary>Shield.io Buttons:</summary> <br> <!--Copy & paste whatever buttons you need!-->

Repo metadata

Social buttons

Call-to-Action buttons

Documentation button

Custom button

<img alt="Custom Shield.io Button" src="https://img.shields.io/badge/Custom-Button-blue.svg?style=flat-square"></img>

<br> <br> <br> <br> <br> <br> <br> <br> <br>

</details> <br> <details><summary>Auto Generated Table Of Contents <b> Demo</b>:</summary> <br> <!------- Table Of Contents Will Auto Generate In Side Of Here ---- > <!-- toc -->

• Features:
• Example and Usage
• Contributing <a href="https://github.com/MarketingPipeline/Awesome-Repo-Template/graphs/contributors"> </a>
• License <a href="LICENSE"> </a>

<!-- tocstop --> </details> <br> <details> <summary> How to setup GitHub bots </summary> <br> These are bots that are prepared and configured for this template. They need to be activated to properly work. <br> <br>

1. The issue_label_bot.yaml file depends on the issue label bot Activate it or check its documentation(✓ highly recommended).
2. The settings.yml file depends on the settings label bot Activate it or check its documentation (optional).
3. The config.yml file depends on the bot welcome bot Activate it or check its documentation and to-do bot (optional).

</details>

Contributing <a href="https://github.com/MarketingPipeline/Awesome-Repo-Template/graphs/contributors"> </a>

Want to improve this template? Create a pull request with detailed changes / improvements! If approved you will be added to the list of contributors of this awesome repo template!

See also the list of
contributors who
participate in this project.

License <a href="LICENSE"> </a>

This project is licensed under the MIT License - see the
LICENSE.md file for
details.