Skip to content

Conversation

@SilvioGregorini
Copy link

@SilvioGregorini SilvioGregorini commented Dec 13, 2019

Small module that allows developers and technical users to directly check relational fields' data from fields tree view and within module form view.

@SilvioGregorini SilvioGregorini changed the title [11.0] Field relation data [12.0] Field relation data Dec 13, 2019
@thomaspaulb
Copy link

/ocabot migration fields_relation_data

/ocabot merge nobump

@OCA-git-bot OCA-git-bot added this to the 12.0 milestone Feb 12, 2024
@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 12.0-ocabot-merge-pr-1743-by-thomaspaulb-bump-nobump, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Feb 12, 2024
Signed-off-by thomaspaulb
@OCA-git-bot OCA-git-bot mentioned this pull request Feb 12, 2024
32 tasks
@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

@thomaspaulb your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-1743-by-thomaspaulb-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.

@thomaspaulb
Copy link

@SilvioGregorini Some pre-commit formality still needs to be done before being able to merge this; could you still do it?

@OCA-git-bot
Copy link
Contributor

@thomaspaulb your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-1743-by-thomaspaulb-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.

@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 Jun 16, 2024
@thomaspaulb
Copy link

@SilvioGregorini ping

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 23, 2024
@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 Oct 27, 2024
@github-actions github-actions bot closed this Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved needs fixing 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.

4 participants