-
Notifications
You must be signed in to change notification settings - Fork 13
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
Various changes & refactoring #6
base: master
Are you sure you want to change the base?
Conversation
I'm done with this PR, you can go ahead and review it. |
client.go
Outdated
PausePipeline(string, string) (*SimpleMessage, error) | ||
UnpausePipeline(string) (*SimpleMessage, error) | ||
UnlockPipeline(string) (*SimpleMessage, error) | ||
PipelineGetInstance(string, int) (*PipelineInstance, error) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm under the impression that methods would generally have to start with an action word. Like Get / Pause / Unlock. Is there a reason we're changing that and moving towards Pipeline
as a prefix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was to have them regrouped in the doc (all the pipeline-related functions together for example) to make them easier to find. But I can change it back.
@ashwanthkumar I changed the name of the functions back to start with the action. |
@aerostitch Thanks for that. I would like to setup the automated build for this project. Can you please give me a few days, until I get that done and I would merge this in? Would that be okay? |
Sure, no problem, go ahead. |
This PR:
agent.go
to use the getJSON methodenvironment.go
to use the getJSON methodGetJobHistory
to use the getJSON methodGetPipelineGroups
to use the getJSON method