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

[16.0][MIG] hr_timesheet_portal #579

Open
wants to merge 10 commits into
base: 16.0
Choose a base branch
from
Open

[16.0][MIG] hr_timesheet_portal #579

wants to merge 10 commits into from

Conversation

AMhadhbi
Copy link
Member

No description provided.

@AMhadhbi AMhadhbi force-pushed the 16.0-mig-hr_timesheet_portal branch from 6929381 to 7e3f149 Compare March 21, 2023 10:42
@AMhadhbi AMhadhbi force-pushed the 16.0-mig-hr_timesheet_portal branch from 7e3f149 to 51ea850 Compare March 21, 2023 10:45
@github-actions
Copy link

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 Jul 23, 2023
@github-actions github-actions bot closed this Aug 27, 2023
@micheledic
Copy link

hello, can we reopen this pr?

@pfranck
Copy link

pfranck commented Nov 25, 2024

Love to reopen it again too

@pedrobaeza pedrobaeza reopened this Nov 25, 2024
@pedrobaeza pedrobaeza removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Nov 25, 2024
@hbrunn
Copy link
Member

hbrunn commented Dec 19, 2024

@pfranck I find it bad manners to ask for reopening a PR and then doing nothing with it

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@hbrunn
Copy link
Member

hbrunn commented Dec 24, 2024

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 16.0-ocabot-merge-pr-579-by-hbrunn-bump-nobump, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Dec 24, 2024
@OCA-git-bot
Merge PR #579 into 16.0
3676526 
Signed-off-by hbrunn
@OCA-git-bot
Copy link
Contributor

@hbrunn your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-579-by-hbrunn-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hbrunn hbrunn hbrunn approved these changes

@thomaspaulb thomaspaulb thomaspaulb approved these changes

Assignees
No one assigned
Labels
approved ready to merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.