Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

current_workspace: get workspace id from file

Open Beginner friendly
  • Is something wrong?
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
json, python
Domain
cli

Research direction

Start by reading the current_workspace implementation and checking how it currently resolves the workspace from the hostname. The issue identifies /etc/rsc/storage.json and its top-level workspace_id key as another source for SRC workspaces with the SRC-OS component. Done when current_workspace can obtain the workspace ID from that file for those workspaces.

Written by the indexing model from the issue text.

Description

current_workspace now looks up the workspace API based on the current workspace's hostname. However, all SRC workspaces with the SRC-OS component also contain the workspace ID in /etc/rsc/storage.json (top-level workspace_id key).

Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UtrechtUniversity/src-api-sdk

All issues in UtrechtUniversity/src-api-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.