feat(devops): automated first-time contributor triage workflow

[itsdakshjain]

Description

This PR introduces an automated triage layer to the Gitbun repository. By utilizing the first-interaction workflow, we can instantly engage new contributors and provide them with the necessary resources (CONTRIBUTING.md) without manual maintainer intervention and reminder for duplicate issue.

Changes

• Created .github/workflows/onboarding-bot.yml.
• Configured state-dependent logic to detect first-time issue creators.
• Standardized the initial greeting to include repository-specific resource links.

Benefits

• Optimized Onboarding: Reduces the "time-to-information" for new contributors.
• Noise Reduction: Uses first-interaction logic to ensure the workflow only triggers once per user, avoiding thread clutter.
• Maintainer Focus: Automates the repetitive task of directing new users to the contribution guidelines.

Closes: #10

Summary by CodeRabbit

• Chores
  • Added an automated onboarding workflow that posts a welcome/checklist to first-time issue contributors and automatically applies a triage label to newly opened issues to improve contributor experience and issue organization.

[UltraBot05]

Earlier: Good fix on separating the label step!

for this change: if: always() on line 32 means the triage label will be applied to every issue, including from existing contributors??
This if: always() label all issues, not just first-timer issues..

Could you please revert the line to
if: steps.welcome_step.outputs.has-first-interaction == 'true'

Another minor change, github Scripts v6 was stable as of summer 2025. current stable is v7. please bump it. to @v7

[UltraBot05]

Closing this PR. The implementation appears to be entirely AI-generated with no attribution or correlation to your own understanding, which goes against GSSoC contribution guidelines (AI usage requires explicit mention and demonstrated understanding of the changes).
Additionally, the self-requested level:advanced and quality:exceptional labels are not justified for a single 41-line YAML file using documented GitHub Actions.

[UltraBot05]

pls discuss first i used my knowldge adn udnrtsodo the whole logic and when my code is running you closed this
Calm down.

First of all. for a yaml addition. we cannot appoint this issue as a level 3 issue.

Please go through the contributor and AI Slop guidelines at
GSSoC AI Conduct

If you'd like to reopen this, please resubmit with:

1. Clear attribution of AI tool usage
2. Your own explanation of every design decision made
3. Accurate difficulty labeling

Also, triaging is not mandated by GSSoC. I am not sure why even would You or me (as a mentor) get points for this.

[itsdakshjain]

pls discuss first i used my knowldge adn udnrtsodo the whole logic and when my code is running you closed this
Calm down.

First of all. for a yaml addition. we cannot appoint this issue as a level 3 issue.

Please go through the contributor and AI Slop guidelines at GSSoC AI Conduct

If you'd like to reopen this, please resubmit with:

1. Clear attribution of AI tool usage
2. Your own explanation of every design decision made
3. Accurate difficulty labeling

Also, triaging is not mandated by GSSoC. I am not sure why even would You or me (as a mentor) get points for this.

@UltraBot05 you can decide that , i am not asking for higher claims if that not valid and also pls go and look into my fork and the issues tab whether all funsiton are working or not . i am not trying to say you did anything wrong but would like to see it through end at good note.

• i understood the claim of traige in issue was my suggestion but i was working on that and is completed and if u think thats not required i can create a pr without it too , but need a clear clarity from you as an reponse in regard to this

thanks

[nirvik34]

Hey @itsdakshjain,

Thanks for sending in your pull request. I’m closing it because it doesn't fit with the GSSoC 2026 contribution rules.

Here’s why:

• Unattributed AI Content: The code and description look like they're mostly generated by AI. Our policy says you need to be upfront if you use AI, no hiding it or claiming it’s entirely your own.
• Scope and Labels Don’t Match: You asked for level:advanced and quality:exceptional labels, but your submission: a 41-line YAML file using basic, documented GitHub Actions doesn’t really line up with those.

Following the program guidelines, I’ll add the gssoc:ai-slop tag to this PR.

You may refer to this: GSSoC AI Conduct

[itsdakshjain]

Hi @nirvik34, i appreciate the feedback. i apologize for the messy commits and the label request, I'm still learning and i definitely overstepped. i will be much more careful with my workflow in the future. Respect your decision and thanks for the time!