Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use secondary directory level as project name #1

Open
jhedstrom opened this issue Jan 16, 2017 · 0 comments
Open

Use secondary directory level as project name #1

jhedstrom opened this issue Jan 16, 2017 · 0 comments
Labels
enhancement

Comments

@jhedstrom
Copy link
Member

The current report has:

  • project name (as in project to be patch)
  • Issue url if available
  • Raw patch url
  • Description (eg, issue number from .make files, but more verbose in composer.json).

Since this is meant to aggregate patch info across projects (as in full site builds), a 5th column should be added, and the name for that should come from the secondary directory structure:

foo_project/composer.json
bar_project/composer.json

This would result in 2 projects in the report.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jhedstrom