llnl / llnl/scraper

Consider migrating to atlassian-python-api

Open
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

code.gov enhancement help wanted
Dominant language
Python
Stars
59
Forks
28
PR merge metrics
No merged PRs in 30d

Description

There is a combined Atlassian Python API package (https://pypi.org/project/atlassian-python-api/) that we might want to see about looking at.

Contributor guide

No contributing guide indexed for this repository

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

Start by reviewing the repository's current source-hosting integrations and compare them with the atlassian-python-api package at the linked PyPI page. Define the migration scope, affected behavior, and validation steps before proposing a change; the issue does not name files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.