Skip to content

[9.0][MIG] project_indicators: Migrated the module from 8.0 to 9.0 #21

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
Open
Chandresh-SerpentCS wants to merge 2 commits into
base: 9.0
Choose a base branch
from
Open

[9.0][MIG] project_indicators: Migrated the module from 8.0 to 9.0 #21

Chandresh-SerpentCS wants to merge 2 commits into from

Conversation

@Chandresh-SerpentCS
Copy link

@Chandresh-SerpentCS Chandresh-SerpentCS commented Jun 21, 2018

project_indicators module migrated from 8.0 to 9.0

@pedrobaeza pedrobaeza added this to the 9.0 milestone Jun 21, 2018
@pedrobaeza pedrobaeza mentioned this pull request Jun 21, 2018
Open
2 tasks
@pedrobaeza pedrobaeza changed the title [MIG] Migrated the module from 8.0 to 9.0 [9.0][MIG] project_indicators: Migrated the module from 8.0 to 9.0 Jun 21, 2018
@Chandresh-SerpentCS
Copy link
Author

Chandresh-SerpentCS commented Jun 29, 2018

@pedrobaeza
Please assign any reviewer to the respective PR. So, we can go ahead.

@pedrobaeza
Copy link
Member

pedrobaeza commented Jun 29, 2018

@Chandresh-SerpentCS I'm afraid that's not the way this works. Reviewing is also a voluntary work. There's no obligation of doing it.

Sometimes, spontaneous volunteers arise because the module is interesting for them, but if you want to get your PR reviewed, you can review other PRs in the same or similar repositories and ask in exchange that they review yours.

dreispt
dreispt requested changes Apr 4, 2020
View reviewed changes
Copy link
Member

@dreispt dreispt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sorry, commit history is missing.

@github-actions
Copy link

github-actions bot commented Jun 8, 2025

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dreispt dreispt dreispt requested changes

Assignees

No one assigned

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Milestone

9.0

Development

Successfully merging this pull request may close these issues.

3 participants

@Chandresh-SerpentCS @pedrobaeza @dreispt