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

subversion_module attribute "force" #9820

Closed
wavilen opened this issue Dec 15, 2014 · 3 comments
Closed

subversion_module attribute "force" #9820

wavilen opened this issue Dec 15, 2014 · 3 comments

Comments

@wavilen
Copy link

wavilen commented Dec 15, 2014

When I set "force=True" in subversion module attributes, it's don't translate to execution "svn export" with "--force" argument.

@ansibot
Copy link
Contributor

ansibot commented Dec 15, 2014

Can You Help Us Out?

Thanks for filing a ticket! I am the friendly GitHub Ansibot.

It looks like you might not have filled out the issue description based on our standard issue template. You might not have known about that, and that's ok too, we'll tell you how to do it.

We have a standard template because Ansible is a really busy project and it helps to have some standard information in each ticket, and GitHub doesn't yet provide a standard facility to do this like some other bug trackers. We hope you understand as this is really valuable to us!.

Solving this is simple: please copy the contents of this template and paste it into the description of your ticket. That's it!

If You Had A Question To Ask Instead

If you happened to have a "how do I do this in Ansible" type of question, that's probably more of a user-list question than a bug report, and you should probably ask this question on the project mailing list instead.

However, if you think you have a bug, the report is the way to go! We definitely want all the bugs filed :) Just trying to help!

About Priority Tags

Since you're here, we'll also share some useful information at this time.

In general tickets will be assigned a priority between P1 (highest) and P5, and then worked in priority order. We may also have some follow up questions along the way, so keeping up with follow up comments via GitHub notifications is a good idea.

Due to large interest in Ansible, humans may not comment on your ticket immediately.

Mailing Lists

If you have concerns or questions, you're welcome to stop by the ansible-project or ansible-development mailing lists, as appropriate. Here are the links:

Thanks again for the interest in Ansible!

@mscherer
Copy link
Contributor

Hi, this bug is for the ansible-modules-core repository, where the subversion module live. And there is already a pull request for that: ansible/ansible-modules-core#506

@bcoca
Copy link
Member

bcoca commented Dec 16, 2014

closing this in favor or report in ansible/ansible-modules-core#370 and fix in ansible/ansible-modules-core#506 as @mscherer pointed out

@bcoca bcoca closed this as completed Dec 16, 2014
@ansible ansible locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants