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

Bitbucket as publish target #487

Closed
mkndn opened this issue Apr 17, 2018 · 6 comments
Closed

Bitbucket as publish target #487

mkndn opened this issue Apr 17, 2018 · 6 comments

Comments

@mkndn
Copy link

mkndn commented Apr 17, 2018

Any chance of adding bitbucket as a publish target?

@mkndn
Copy link
Author

mkndn commented Apr 18, 2018

Can you give more details on the help that you need. I will see if i can be of any help. I need to see if i have the required environment setup.

@malept
Copy link
Member

malept commented Apr 18, 2018

The "help wanted" label is on this issue because we would need to have someone file a pull request for the feature. We don't currently have any documentation on how to create publisher plugins for 6.x, you'd have to look at the existing ones in the repository.

@mkndn
Copy link
Author

mkndn commented Apr 19, 2018

@malept Is that the reason why I'm not able to publish it to GitHub? I understood how "helpwanted" works now. Thank you

@vintprox
Copy link
Contributor

vintprox commented Jul 24, 2018

I'd find publishing git repositories in any service more modular and futureproof than to specific ones. And it requires some mature solution for this task (without reinventing the bicycle, I guess?), so without pain in specifying SSL, passwords, tokens stuff or whatevs.

@malept
Copy link
Member

malept commented Jul 24, 2018

Publishing to a git repository should be in a separate issue, although I don't know whether we'd want to support that as a first-party plugin.

@vintprox
Copy link
Contributor

vintprox commented Jul 24, 2018

Definitely third-party. Most developers prefer to do publishing by themselves: like describing new commits, resolving merge conflicts, squashing. All of that is already possible with git tool. Actually, if we wanna best ideas for "publishers" we gotta checkout with the average user's choice, which is another issue.

lukebatchelor added a commit that referenced this issue Sep 11, 2018
MarshallOfSound pushed a commit that referenced this issue Sep 12, 2018
* feat(publisher-bitbucket): initial publish of @electron-forge/publisher-bitbucket

ISSUES CLOSED: #487

* feat(publisher-bitbucket): adds \`replaceExistingFiles\` config for publisher-bitbucket
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants