restsharp / restsharp/RestSharp

import directives

Open
#2,395 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
9.8k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

import os

base_dir = "/mnt/agents/output/artifacts/by-end-of-August"

Create the directory structure first

os.makedirs(f"{base_dir}/01-real-life", exist_ok=True)
os.makedirs(f"{base_dir}/02-farming-sim", exist_ok=True)
os.makedirs(f"{base_dir}/03-notes", exist_ok=True)
os.makedirs(f"{base_dir}/backups", exist_ok=True)

1. Main instructions file

instructions = """# Instructions for Workspace

Directory Structure (by-end-of-August)

01-real-life

Purpose: Store real-life artifacts, observations, and field data.
Guidelines: Keep raw data separate from processed outputs.

02-farming-sim

Purpose: Farming simulation outputs, configs, and results.
Guidelines: Version all simulation parameters. Tag runs with dates.

03-notes

Purpose: General notes, meeting minutes, and scratch pads.
Guidelines: Use dated filenames (YYYY-MM-DD-topic.md). Archive monthly.

backups

Purpose: Automated and manual backups of the above.
Guidelines: Retain 30-day rolling window. Compress archives older than 7 days.

Sender Directives

  1. All files must include a timestamp header.
  2. Use consistent naming: kebab-case for files, snake_case for internal refs.
  3. Cross-reference between 01, 02, and 03 using relative paths.
  4. Backups run at 23:59 UTC daily — do not modify backup/ during the window.
  5. Report completion status to sender before each subfolder exceeds 100 MB.
    """

with open(f"{base_dir}/INSTRUCTIONS.md", "w") as f:
f.write(instructions)

2. Directive file for sender

directives = """# DIRECTIVES — To Sender

Operational Directives

  • D1: Verify directory permissions before each write batch.
  • D2: Log all file creations in 03-notes/activity-log.md.
  • D3: Notify on completion or failure within 5 minutes.
  • D4: Maintain read-only mirrors in backups/ after each session.
  • D5: Do not delete — archive and mark with .archived suffix.

Communication Protocol

  • Status updates go to sender via the agreed channel.
  • Use directive codes (D1–D5) when referencing rules.
  • Escalate permission issues immediately; do not retry silently.
    """

with open(f"{base_dir}/DIRECTIVES.md", "w") as f:
f.write(directives)

3. Per-folder directive stubs

for folder, desc in [
("01-real-life", "Real-life data ingestion directives"),
("02-farming-sim", "Simulation run directives"),
("03-notes", "Note-taking and logging directives"),
("backups", "Backup and recovery directives")
]:
stub = f"# {desc}\n\nSee ../INSTRUCTIONS.md and ../DIRECTIVES.md for full protocol.\n\n## Folder-Specific Rules\n- Created: 2026-08-03\n- Owner: sender\n- Review cycle: weekly\n"
with open(f"{base_dir}/{folder}/README.md", "w") as f:
f.write(stub)

print("Created:")
for root, dirs, files in os.walk(base_dir):
level = root.replace(base_dir, '').count(os.sep)
indent = ' ' * 2 * level
print(f'{indent}{os.path.basename(root)}/')
subindent = ' ' * 2 * (level + 1)
for file in files:
print(f'{subindent}{file}')

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no RestSharp file, test, or entry point; its concrete paths are under /mnt/agents/output/artifacts/by-end-of-August and describe generated Markdown files. Start by confirming the intended RestSharp change with the reporter rather than running the embedded script. Done should be a specific repository change with an identified validation step.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.