Submit package to packagist

Open
#17 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
release, tooling

Research direction

Start with the root composer.json and inspect the package metadata and current code layout. Verify what Packagist requires for this repository, then check whether the optional PSR-4 reorganization is in scope. Done means the package is available on Packagist and any agreed autoloading changes are reflected consistently.

Written by the indexing model from the issue text.

Description

There is a composer.json file now, but the package isn't available on packagist so adding a 'repository' object to the root composer.json is required.

May want to consider reorganizing the code into PSR-4 format as well.

Dominant language
PHP
Stars
68
Forks
16
No merged PRs in 30d

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.

More from binaryage/firelogger.php

All issues in binaryage/firelogger.php

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.