Skip to content

Commit 77c4867

Browse files
authored
Merge branch 'main' into fix/sync-metadata-workflow
2 parents 59eadb3 + bfb7d6c commit 77c4867

28 files changed

+1235
-897
lines changed

.github/workflows/autolabel-pr-issue.yml

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
name: Sync Issue Metadata to PR
22

33
on:
4-
pull_request_target:
4+
pull_request: # Changed from pull_request_target for testing
55
types: [opened, edited, synchronize, reopened]
66

77
permissions:
@@ -35,10 +35,10 @@ jobs:
3535
/(?:close[sd]?|fix(?:e[sd])?|resolve[sd]?)\s+#(\d+)/gi,
3636
/#(\d+)/g
3737
];
38-
38+
3939
const issueNumbers = new Set();
4040
const text = prTitle + ' ' + prBody;
41-
41+
4242
for (const pattern of patterns) {
4343
for (const match of text.matchAll(pattern)) {
4444
issueNumbers.add(match[1]);
@@ -90,7 +90,7 @@ jobs:
9090
repo: context.repo.repo,
9191
issue_number: parseInt(issueNumber, 10)
9292
});
93-
93+
9494
console.log(`Syncing metadata from Issue #${issueNumber} to PR #${prNumber}`);
9595
9696
// --- Sync Labels safely using addLabels ---
@@ -123,7 +123,6 @@ jobs:
123123
issue_number: prNumber,
124124
body: `✅ Synchronized metadata from Issue #${issueNumber}:\n- Labels: ${issueLabels.length > 0 ? issueLabels.join(', ') : 'None'}\n- Milestone: ${issue.milestone ? issue.milestone.title : 'None'}`
125125
});
126-
127126
} catch (error) {
128127
console.error(`Error syncing issue #${issueNumber} to PR #${prNumber}:`, error);
129128
}
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
# Anurag Hazra's GitHub Readme Cards
2+
3+
This is the foundational tool for dynamic profile statistics. It uses a serverless function to generate SVGs (Scalable Vector Graphics) displaying **real-time data** pulled directly from your GitHub profile. These cards are the quickest and most popular way to upgrade your Readme.
4+
5+
| Feature | Description |
6+
| :--- | :--- |
7+
| **Stats Card** | Shows core metrics: total stars, commits (in the last year), pull requests, and contribution count. |
8+
| **Language Card** | Displays your usage breakdown of **top languages** across your repositories (excluding forks). |
9+
10+
### Setup Example (Stats & Language Cards)
11+
12+
To use these cards, you simply embed them as images in your `README.md`. **Replace `YOUR_USERNAME` with your actual GitHub username.** The code below uses the popular `buefy` theme.
13+
14+
```markdown
15+
## My GitHub Stats
16+
17+
[![GitHub Stats](https://github-readme-stats.vercel.app/api?username=YOUR_USERNAME&show_icons=true&theme=buefy&hide_rank=true)](https://github.com/anuraghazra/github-readme-stats)
18+
19+
## Top Languages
20+
21+
[![Top Langs](https://github-readme-stats.vercel.app/api/top-langs/?username=YOUR_USERNAME&layout=compact&theme=buefy&exclude_repo=recode-hive-docs,test-repo)](https://github.com/anuraghazra/github-readme-stats)
22+
23+
### Customization: Themes and Layouts
24+
25+
You can drastically change the appearance and content of your cards by adding parameters to the URL string (e.g., `&param=value`).
26+
27+
#### 🎨 Popular Themes (`&theme`)
28+
29+
The &theme= parameter allows you to apply a full color scheme. Try one of these popular options by adding it to the API URL:
30+
31+
- dark: Standard dark mode, high contrast.
32+
- buefy: Bright blue and purple scheme (used in the example above).
33+
- synthwave: Retro 80s neon look.
34+
- onedark: A popular editor theme, often used by developers.
35+
- solarized_light: A classic light theme option.
36+
37+
38+
#### 📐 Layout Options (`&layout`)
39+
40+
This parameter is most commonly used for the Top Languages card to optimize space:
41+
42+
- default: (Used on the Stats Card) A larger vertical layout with distinct borders.
43+
- compact: (Recommended for Language Card) Displays language bars horizontally, resulting in a much shorter, more compact card.
44+
45+
#### Other Key Parameters
46+
47+
| Parameter | Example Value | Description |
48+
| :--- | :--- | :--- |
49+
| `&show_icons=` | `show_icons=true` | Displays icons next to each stat label (highly recommended). |
50+
| `&hide=` | `hide=issues,prs` | Hides specific statistics, like issues or pull requests, if you prefer a cleaner look. |
51+
| `&title_color=` | `title_color=007bff` | Sets a custom hexadecimal color for the card title. |
52+
| `&exclude_repo=` | `exclude_repo=test-repo,docs` | Hides specific repositories from the language calculations.|
53+
54+
⚠️ **Important Note on Language Calculations:** The Top Languages card calculates language usage from all public repos you own. To ensure the card accurately reflects your coding focus (and not just boilerplate files), it is strongly recommended to use the &exclude_repo= parameter to ignore repositories containing auto-generated documentation or simple configuration.
55+
56+
🔗 Relevant Repo: ![Anurag Hazra's GitHub Readme Stats](https://github.com/anuraghazra/github-readme-stats)
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
# Snake Contribution Animation 🐍
2+
3+
The Snake Contribution Animation is a visually unique and engaging way to represent your yearly activity. This feature adds a looping GIF or SVG of a "snake" chasing and consuming your contribution blocks, creating a dynamic element on your profile.
4+
5+
### How the Snake Animation Works
6+
7+
Unlike static image cards, the snake animation is a generated file (usually an SVG). This file must be **generated by a script and committed** back to your profile repository regularly to stay up-to-date with your latest activity. This entire process is fully automated using a **GitHub Action** that runs on a schedule.
8+
9+
---
10+
11+
## GitHub Action Setup
12+
13+
To automate the snake animation, you must create a YAML workflow file named **`snake.yml`** inside your profile repository's `.github/workflows/` directory.
14+
15+
### 1. The Workflow File (`snake.yml`)
16+
17+
Use the following content for your workflow file. This configuration uses the recommended `lowlighter/metrics` action, sets it to run daily, and ensures the necessary permissions are granted.
18+
19+
```yaml
20+
name: Generate Snake Animation
21+
22+
on:
23+
schedule:
24+
# Runs at 1 AM UTC every day
25+
- cron: "0 01 * * *"
26+
workflow_dispatch:
27+
# Allows manual trigger via the GitHub Actions tab
28+
29+
jobs:
30+
generate:
31+
runs-on: ubuntu-latest
32+
permissions:
33+
contents: write # CRITICAL: This grants permission to commit the new file
34+
35+
steps:
36+
- uses: actions/checkout@v4
37+
- uses: lowlighter/metrics@latest # Use the metrics action
38+
39+
with:
40+
# REQUIRED: GitHub token (automatically provided by GitHub)
41+
token: ${{ secrets.GITHUB_TOKEN }}
42+
43+
# Output configuration
44+
output_name: output/github-snake.svg
45+
user: ${{ github.repository_owner }} # Automatically detects your username
46+
47+
# Plugin configuration for the snake
48+
template: snake
49+
base: "" # Base is disabled to focus only on the snake plugin
50+
plugin_isocalendar: yes
51+
plugin_isocalendar_duration: full-year
52+
```
53+
Once your workflow runs successfully (you can check the Actions tab on GitHub), the generated file will be saved to your repository. Embed the image in your main README.md using the path where the action saved the file:
54+
55+
```markdown
56+
## My 2024 GitHub Activity
57+
58+
![Snake Animation](https://raw.githubusercontent.com/YOUR_USERNAME/YOUR_USERNAME/output/github-snake.svg)
59+
```
60+
61+
(Replace YOUR_USERNAME with your actual GitHub username.)
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Trophy Case and Contribution Streaks
2+
3+
These tools complement the core GitHub Readme Stats by focusing on **gamification** and **consistency**, turning your contributions into visible achievements.
4+
5+
### GitHub Trophy Case 🏆
6+
7+
This service awards different virtual "trophies" based on your activity, such as total star count, number of commits, number of followers, and maintaining contribution streaks. It’s an excellent motivator for long-term engagement.
8+
9+
**Setup Example:**
10+
To include the trophy case, simply embed the SVG image link in your Readme, replacing `YOUR_USERNAME`:
11+
12+
### My Trophy Case
13+
14+
[![GitHub Trophies](https://github-profile-trophy.vercel.app/?username=YOUR_USERNAME&theme=gruvbox&no-frame=true)](https://github.com/ryo-ma/github-profile-trophy)
15+
16+
🔗 Relevant Repo: ![ryo-ma/github-profile-trophy](https://github.com/ryo-ma/github-profile-trophy)
17+
18+
### GitHub Streaks 🔥
19+
This card displays your current streak of contributions and your longest historical streak, promoting a daily habit of coding. Seeing your streak number grow can be a powerful psychological push!
20+
21+
**Setup Example:**
22+
23+
[![GitHub Streak](https://github-readme-streak-stats.herokuapp.com/?user=YOUR_USERNAME&theme=highcontrast&date_format=j+M+Y)](https://github.com/DenverCoder1/github-readme-streak-stats)
24+
25+
🔗 Relevant Repo: ![DenverCoder1/github-readme-streak-stats](https://github.com/DenverCoder1/github-readme-streak-stats)
26+
27+
💡 Tip: To maintain a streak, remember that contributions count if they are made within a 24-hour period, based on UTC time.
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# 🎨 Fun GitHub Profile Customizations
2+
3+
Your GitHub profile Readme is a prime piece of digital real estate. It’s more than just a list of code repositories—it's your developer brand, your digital workshop, and your **first impression** on the global coding community. Customizing it is essential for promoting the dynamic developer culture of Recode Hive and maximizing your personal visibility.
4+
5+
---
6+
7+
## Why Customize?
8+
9+
### 🛠️ The Essential First Step: Create Your Profile Repository
10+
11+
Before you can add any dynamic stats or flair, you must complete the single, most important requirement:
12+
13+
**Requirement:** You must create a **public GitHub repository** named *exactly* the same as your GitHub username (e.g., if your username is `recode`, the repo must be `recode/recode`). When you create this special repository, GitHub will automatically use its `README.md` file as the content for your public profile page.
14+
15+
### Why Personalization Pays Off
16+
17+
Once your profile repo is set up, customization offers tangible benefits that go far beyond aesthetics:
18+
19+
1. **First Impressions and Engagement:** A creative, customized profile is immediately **engaging and memorable**, encouraging visitors (mentors, recruiters, or collaborators) to spend more time exploring your work. By highlighting your key skills and active projects upfront, you dramatically increase the chances of a meaningful connection.
20+
21+
2. **Highlight Activity and Commitment:** Dynamic cards displaying stats for your **total commits, contribution streaks, and top languages** automatically validate your commitment to continuous learning and development. This proof-of-work is far more convincing than a simple claim on a resume.
22+
23+
3. **Showcase Your Identity and Skills:** Customization allows you to highlight projects that matter most to you, whether it's a specific Recode Hive project or a new language you're mastering. Your profile becomes a curated **showcase of your specific expertise** and personality.
24+
25+
4. **Professional Polish and Detail:** A well-structured, customized profile demonstrates **attention to detail, technical flair, and ownership**. These soft skills are highly valued in any professional development setting.

docs/GitHub/GitHub-basics/create-github-repo.md

Lines changed: 21 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -7,29 +7,33 @@ tags: [GitHub, GitHub-development, document-structure, GitHub repo,]
77
description: In this tutorial, you will learn about the how to create a GitHub repo by Online GUI interface.
88
---
99

10-
In the previous post we spoke about commit, fork, clone, in this post we gonna deep dive into the terminology by creating a GitHub Repository from the Scratch.
11-
Inorder to create a project and host, the repository is a place where you add all your program code files and other documentation.
10+
In the previous post, we learned about commit, fork and clone. In this post, we are going to take a deep dive into the terminology by creating a GitHub Repository from scratch.
11+
To create and host a project, the repository is a place where you add all your program code files and other documentation.
1212

1313
### Prerequisites
1414

15-
- 1. You should have a Github account
16-
- 2. Should have a basic understanding of how Git works/ and Git running in your OS.
15+
- 1. You must have a GitHub account.
16+
- 2. You must also have a basic understanding of how Git works and ensure Git is installed and running on your operating system.
1717

1818
### How to create Github Repository
1919

20-
**Step 1:** Go to GitHub page, by default you will be in the Home page as shown below, Step 1 requires you to click on the ``+`` Icon and from the drop down click on the ``New Repository``.
20+
**Step 1:** Go to the GitHub website. By default, you will be on the Home page as shown below. Click on the ``+`` icon in the top-right corner, and from the dropdown, select ``New Repository``.
2121

2222
<BrowserWindow url="https://github.com" bodyStyle={{padding: 0}}>
2323
[![GitHub](./assets/1-GitHub-repo.png)](https://github.com/sanjay-kv)
2424
</BrowserWindow>
25-
**Step 2:** Specify the name of the Project, make It public or private, for this tutorial you will make it public, Once the repository is gone private the project admin have to give permission or manually added other GitHub user to collaborate or make it visible. This is usual application in the organisation level. The next step check on the readme file, this allows you to create a ``readme.md`` file along with the repository creation. Then click on ``Create repository`` on the button below.
25+
**Step 2:** Specify the name of the project and choose whether to make it public or private. For this tutorial, we’ll make it public.
26+
27+
Once a repository is made private, the project admin must manually grant permission to other GitHub users to collaborate or view it. This is a common practice at the organizational level.
28+
29+
Next, check the box to include a README file—this will automatically create a ``README.md`` file along with the repository. Finally, click on ``Create repository`` at the bottom.
2630

2731

2832
<BrowserWindow url="https://github.com/new" bodyStyle={{padding: 0}}>
2933
[![GitHub](./assets/4-git-gui-install.png)](https://github.com/sanjay-kv)
3034
</BrowserWindow>
3135

32-
Upon creation you will get a screen like this below, the explanation of each elements is mentioned below.
36+
Once the repository is created, you’ll see a screen like the one below. The explanation of each elements is mentioned below.
3337

3438
<BrowserWindow url="https://github.com/sanjay-kv/Git-Demo" bodyStyle={{padding: 0}}>
3539
[![GitHub](./assets/5-git-add-file.png)](https://github.com/sanjay-kv)
@@ -44,17 +48,17 @@ Upon creation you will get a screen like this below, the explanation of each ele
4448
- **`<body>`**: Contains the visible content of the document.
4549
- **`<!-- Your content goes here -->`**: Represents a comment that is not displayed in the browser.
4650

47-
## Changing Readme and Adding more files.
51+
## Changing the README and adding more files.
4852

49-
Im going to add my resume and add my name as heading to the ``readme.md`` file
53+
I’m going to add my resume and include my name as a heading in the ``README.md`` file.
5054

5155
<BrowserWindow url="https://github.com/sanjay-kv/Git-Demo" bodyStyle={{padding: 0}}>
5256
[![GitHub](./assets/6-edit-file-git.png)](https://github.com/sanjay-kv)
5357
</BrowserWindow>
5458

5559
### Adding Markdown Language
5660

57-
Below is a visual representation of the basic HTML document structure:
61+
Below is a visual representation of a basic HTML document structure:
5862
```html title="readme.md"
5963
# Git-Demo
6064
This is a demo installation via GUI
@@ -66,7 +70,7 @@ This readme contains my resume, please refer to the attached file in the repo.
6670

6771
### Browser Rendering
6872

69-
When the above HTML code is rendered in a browser, it will display the following content:
73+
When the above HTML code is rendered in a browser, it will display the following output:
7074

7175
<BrowserWindow url="https://github.com/sanjay-kv/Git-Demo/edit/main/README.md">
7276
<>
@@ -92,13 +96,13 @@ When the above HTML code is rendered in a browser, it will display the following
9296

9397
## Committing the changes.
9498

95-
Im going to add my resume and add my name as heading to the ``readme.md`` file
99+
I'm going to add my resume and include my name as heading to the ``README.md`` file.
96100

97101
<BrowserWindow url="https://github.com/sanjay-kv/Git-Demo/edit/main/README.md" bodyStyle={{padding: 0}}>
98102
[![GitHub](./assets/7-commit-the-changes.png)](https://github.com/sanjay-kv)
99103
</BrowserWindow>
100104

101-
Here is the step where they need adding additional comments
105+
This is the step where you need to add additional comments.
102106

103107
<BrowserWindow url="https://github.com/sanjay-kv/Git-Demo/edit/main/README.md" bodyStyle={{padding: 0}}>
104108
[![GitHub](./assets/8-commit-message.png)](https://github.com/sanjay-kv)
@@ -112,24 +116,24 @@ https://github.com/sanjay-kv/Git-Demo
112116

113117
### Now let's upload your resume
114118

115-
Im going to add my resume and add my name as heading to the ``readme.md`` file
119+
I'm going to add my resume and include my name as heading to the ``README.md`` file.
116120

117121
<BrowserWindow url="https://github.com/sanjay-kv/Git-Demo/edit/main/README.md" bodyStyle={{padding: 0}}>
118122
[![GitHub](./assets/10-add-git-file.png)](https://github.com/sanjay-kv)
119123
</BrowserWindow>
120124

121-
Here is the step where they need adding additional comments
125+
This is the step where you need to add additional comments.
122126

123127
<BrowserWindow url="https://github.com/sanjay-kv/Git-Demo/upload/main" bodyStyle={{padding: 0}}>
124128
[![GitHub](./assets/11-add-file-commit-git.png)](https://github.com/sanjay-kv)
125129
</BrowserWindow>
126130

127-
Now you will be able to see the uploaded resume.
131+
You will now be able to see the uploaded resume in your repository.
128132

129133
### Watch the video Tutorial
130134

131135
<iframe width="880" height="480" src="https://www.youtube.com/embed/XWjx-RjmhRM?list=PLrLTYhoDFx-kiuFiGQqVpYYZ56pIhUW63" title="How to create your first GitHub repository" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
132136

133137
## Conclusion
134138

135-
In this tutorial, you learned about the syntax and structure of HTML. HTML syntax consists of elements, tags, and attributes that define the structure and content of a web page. An HTML document follows a basic structure with elements like `<!DOCTYPE html>`, `<html>`, `<head>`, `<title>`, `<meta>`, and `<body>`. Understanding HTML syntax and structure is essential for creating web pages and applications.
139+
In this tutorial, you learned about the syntax and structure of HTML. HTML syntax consists of elements, tags and attributes that define the structure and content of a web page. A HTML document follows a basic structure with elements like `<!DOCTYPE html>`, `<html>`, `<head>`, `<title>`, `<meta>` and `<body>`. Understanding HTML syntax and structure is essential for creating web pages and applications.

0 commit comments

Comments
 (0)