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.

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

[15.0] Replace 'Camptocamp SA' with 'Camptocamp' #247

Open
wants to merge 2 commits into
base: 15.0
Choose a base branch
from

Conversation

vvrossem
Copy link

This pull request contains changes to replace 'Camptocamp SA' with 'Camptocamp' in manifest.py files for branch 15.0.

@OCA-git-bot
Copy link
Contributor

Hi @yankinmax, @ivantodorovich,
some modules you are maintaining are being modified, check this out!

Copy link

@ivantodorovich ivantodorovich left a comment

Choose a reason for hiding this comment

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

/ocabot merge nobump

@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). 🤖

@OCA-git-bot
Copy link
Contributor

Sorry @ivantodorovich you are not allowed to merge.

To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons.

If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the maintainers key of its manifest.

@Saran440
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

@Saran440 The merge process could not start, because command git fetch --quiet --force --prune https://github.com/OCA/hr-expense 'refs/heads/*:refs/heads/*' failed with output:

fatal: unable to access 'https://github.com/OCA/hr-expense/': gnutls_handshake() failed: The TLS connection was non-properly terminated.

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 Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved ready to merge stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants