[Good First Issue]: Update bot-inactivity-unassign workflow to use self hosted runner

[AntonioCeppellini]

🆕🐥 Newcomer Friendly

This Good First Issue is a guided, well-scoped task intended for new contributors to the Hiero Python SDK.

What you’ll do

• ✅ understand how the repository is structured
• ✅ practice the standard contribution workflow
• ✅ submit and merge a pull request

Support

A maintainer or mentor actively monitors this issue and will help guide it to completion.

Important

This issue does not require prior domain knowledge.

• No Hiero or Hedera experience needed
• No distributed ledger background required
• Basic Python and Git are sufficient

Note

⏱️ Typical time to complete: 30–90 minutes (once setup is done)
🧩 Difficulty: Small, well-contained change
🎓 Best for: New contributors

🏁 Completion
When this issue is complete, you will have:

• ✅ Solved a real issue
• ✅ A merged pull request in the Hiero Python SDK
• ✅ Your name in the project history
• ✅ Confidence to take on larger issues next

👾 Issue description

Right now our .github/workflows/bot-inactivity-unassign.yml is running on ubuntu-latest but can be upgraded to run on hl-sdk-py-lin-md :D

💡 Proposed Solution

Switch from ubuntu-latest to hl-sdk-py-lin-md.

🛠️ Implementation Steps

go on the file .github/workflows/bot-inactivity-unassign.yml and change the line from:

runs-on: ubuntu-latest

to

runs-on: hl-sdk-py-lin-md

📋 Step-by-Step Setup Guide

Suggestions:

• Visual Studio (VS) Code: Guide

• GitHub Desktop: Guide

• Hedera Testnet Account with root .env file: Guide

• Create a GPG key linked to GitHub: Guide

Setup the Hiero Python SDK for development

• Fork Create an online and local copy of the repository: Guide

• Connect origin with upstream: Guide

• Install Packages and protobufs: Guide (or Windows Setup Guide for Windows users)

• Sync Main pull any recent upstream changes: Guide

You are set up! 🎉

📋 Step-by-step contribution guide

✅ Get ready

• Claim the issue: comment /assign: Guide. Pull requests created without being assigned will be automatically closed.

• Double check the Issue and AI plan: carefully re-read the issue description and the CodeRabbit AI plan

• Ask questions early: ask on Discord, your @mentor (Python SDK help) and the @good_first_issue_support_team (setup and workflow help)

• Sync with main: pull the latest upstream changes Guide

• 💡 Tip: Before coding, leave a short comment describing what you plan to change. We’ll confirm you’re on the right track.

🛠️ Solve the Issue

• Create a branch from main: Guide

• Implement the solution: follow the implementation steps in the issue description.

• Commit with DCO and GPG signing: commit changes using: git commit -S -s -m "chore: your message", Guide

• Add a .CHANGELOG.md entry: under the appropriate [UNRELEASED] section and commit as git commit -S -s -m "chore: changelog entry" Guide

🚀 Create the pull request

• Push your commits: push your branch to your fork git push origin your-branch-name

• Open a pull request: here guide

• Complete the PR description: briefly describe your changes, Guide

• Link the Issue: link the issue the PR solves in the PR description, Guide. Pull requests created without a linked issue will be automatically closed.

• Submit the pull request: click **Create pull request** 🎉

✅ Acceptance criteria

To be able to close this issue, the following criteria must be met:

• The issue is solved: I’ve carefully read and implemented the issue requirements

• I did not add extra changes: I did not modify anything beyond what is described in the issue

• Behavior: All other existing features continue to work as before

• Checks and feedback: All checks pass and any requested changes have been made

🧭 Getting help if you’re stuck

If questions come up, don’t spend more than 20 minutes blocked.

Tip

• Comment on this issue and tag @good_first_issue_support_team or @mentor_name
• Ask for help in Discord

---

🤔 What to expect after submitting a PR

Once you open a pull request, here’s what happens next.

🤖 1. Automated checks
A small set of automated checks must pass before merging (signing, changelog, tests, examples, code quality).
Open any failed check to see details.

---

🤝 2. AI feedback (CodeRabbit)
CodeRabbit AI may suggest improvements or flag issues.
Feedback is advisory — use what’s relevant and helpful.

---

😎 3. Team review
A Python SDK team member reviews your PR within 1–3 days.
You may be asked to make changes or your PR may be approved.
Approved PRs are usually merged within one day.

🔄 Merge conflicts (sometimes)
Conflicts can happen and are normal as the SDK updates.
Changelog conflicts can be resolved online in the PR in the merge editor, accepting both entries
Others may require rebasing.

---

🤖 AI usage guidelines

You’re welcome to use AI tools while working on this issue.

Many contributors do — especially for:

• understanding unfamiliar code
• drafting small refactors
• sanity-checking approaches

Use AI responsibly:

• review suggestions carefully
• apply changes incrementally
• test as you go

If in doubt, ask — maintainers are happy to help.

🤔 Additional Help

First Points of Contact:

• Discord
• Comment with @mentor_name (for Python SDK questions)
• Comment with @hiero-ledger/hiero-sdk-good-first-issue-support (for setup and workflow questions)
  The more you ask, the more you learn and so do we!

Documentation:

• README.md

• CONTRIBUTING.md

• Project Structure

• DCO and Verified Signing Guide

• Changelog Guide

• Rebasing Guide

• Merge Conflicts Guide

• Linking Issues Guide

• Workflow Guide

• Pin Github Actions Guide

• Running Examples

• Testing on Forks

• General Training

• General SDK Developer Docs

Calls:

• Get hands-on-help by our expert team at our Office Hours
• Learn, raise issues and provide feedback at Community Calls

[exploreriii]

Issue is open to assignment

[emanisaikumar01]

/assign

[github-actions]

👋 Hi @emanisaikumar01, welcome to the Hiero Python SDK community!

You've been assigned this Good First Issue. Your on-call mentor today from @hiero-ledger/hiero-sdk-python-triage is @undefinedIsMyLife, and the Good First Issue Support Team is @hiero-ledger/hiero-sdk-good-first-issue-support.
We’re here to help you get your first PR merged successfully 🚀

---

Step 1: Read the task

• Open the issue description, carefully read the requirements and workflow
• Read any linked documentation
• Make sure you understand the expected outcome
  If anything is unclear, ask your mentor before writing code.

---

Step 2: Tell us your plan (in this thread)

Reply here with:

• What you think the task is
• What you plan to change to solve the issue requirement and no more
• Any questions you have
  This means we can guide you early on, helping you to have a more stress free experience

---

Step 3: Get the right kind of help

Finishing your first PR can be really hard. We are here to help you - please ask us!

🛠 Good First Issue Support Team (@hiero-ledger/hiero-sdk-good-first-issue-support)
Use them for workflow and GitHub issues, such as:

• Failing CI checks
• Commit signing problems
• Merge conflicts
• Git/GitHub errors
  They can also jump on a call if needed.

🐍 Your Mentor (@undefinedIsMyLife)
Use your mentor for Python and code guidance, such as:

• Which files to edit
• How to structure your solution
• Docstring and code style questions
• Making sure your PR meets the issue requirements

💬 Discord (for fast help)
Guide: Join the Python SDK Discord
Use Discord when you need immediate answers from the community, like:

• What docs to read
• How to unblock yourself quickly
• Clarifying next steps in real time

---

Mentor: @undefinedIsMyLife
Mentee: @emanisaikumar01
If you're enjoying the SDK, consider ⭐️ starring the repository so it's easy to find later.
Happy building!
— Python SDK Team

[github-actions]

@coderabbitai plan

[coderabbitai]

Coding Plan

Summary

• Single-line change replacing ubuntu-latest with hl-sdk-py-lin-md in the workflow's runs-on field
• Follows the established pattern already used by four other bot workflows in the repository
• No functional changes to the workflow logic; only the execution environment changes

Implementation Steps

Update Workflow Runner Configuration

Update the bot-inactivity-unassign workflow to use the self-hosted runner, following the established pattern used by other bot workflows in the repository.

Change runs-on Value

Modify the workflow to use the self-hosted runner instead of the GitHub-hosted runner.

• Update .github/workflows/bot-inactivity-unassign.yml line 21: change runs-on: ubuntu-latest to runs-on: hl-sdk-py-lin-md
• No other modifications are required to this file or any other files

🤖 Prompt for AI agents

Update the `runs-on` value in `.github/workflows/bot-inactivity-unassign.yml` to
replace the GitHub-hosted runner with the self-hosted runner.

- In `.github/workflows/bot-inactivity-unassign.yml`, locate line 21 where
`runs-on: ubuntu-latest` is defined
- Change `runs-on: ubuntu-latest` to `runs-on: hl-sdk-py-lin-md`
- No other files or lines require modification

Research

The repository contains GitHub Actions workflows in .github/workflows/. The bot-inactivity-unassign.yml workflow runs a daily scheduled job to unassign inactive contributors from issues and PRs. Currently, this workflow uses ubuntu-latest as its runner, while four other bot workflows (bot-assignment-check.yml, bot-beginner-assign-on-comment.yml, bot-coderabbit-plan-trigger.yml, and bot-community-calls.yml) already use the self-hosted runner hl-sdk-py-lin-md. This change brings the inactivity bot in line with the established pattern.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Update the `runs-on` value in `.github/workflows/bot-inactivity-unassign.yml` to
replace the GitHub-hosted runner with the self-hosted runner.

- In `.github/workflows/bot-inactivity-unassign.yml`, locate line 21 where
`runs-on: ubuntu-latest` is defined
- Change `runs-on: ubuntu-latest` to `runs-on: hl-sdk-py-lin-md`
- No other files or lines require modification

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!

[emanisaikumar01]

Thanks for assigning the issue.

My understanding of the task is to update the GitHub Actions workflow runner in .github/workflows/bot-inactivity-unassign.yml.

I plan to change the line:

runs-on: ubuntu-latest

to

runs-on: hl-sdk-py-lin-md

so that the workflow uses the repository’s self-hosted runner, consistent with the other bot workflows. I will not modify any other lines or files.