How to deal with coworker committing and pushing nonsense changes directly to master?
Given that I am the least experienced in this place I thought in the beginning it's normal what a coworker is doing, committing and pushing nonsense changes directly to master including broken parts. I used to do the same in very extreme situations when fixing something broken or under time constraints (small sync to showcase), this doesn't seem to be the case.
For example today I am being notified of merge conflict because of: adding 4 new lines, commenting out 2 logging messages!
Maybe the reason is to be on top on developers list with the most commits to get raises (just like the nonsense competition on contribution graph on GitHub), but I am getting distracted now very often with these nonsense pushes to master.
How can I approach this issue as the least experienced person here?
professionalism communication colleagues
New contributor
add a comment |
Given that I am the least experienced in this place I thought in the beginning it's normal what a coworker is doing, committing and pushing nonsense changes directly to master including broken parts. I used to do the same in very extreme situations when fixing something broken or under time constraints (small sync to showcase), this doesn't seem to be the case.
For example today I am being notified of merge conflict because of: adding 4 new lines, commenting out 2 logging messages!
Maybe the reason is to be on top on developers list with the most commits to get raises (just like the nonsense competition on contribution graph on GitHub), but I am getting distracted now very often with these nonsense pushes to master.
How can I approach this issue as the least experienced person here?
professionalism communication colleagues
New contributor
add a comment |
Given that I am the least experienced in this place I thought in the beginning it's normal what a coworker is doing, committing and pushing nonsense changes directly to master including broken parts. I used to do the same in very extreme situations when fixing something broken or under time constraints (small sync to showcase), this doesn't seem to be the case.
For example today I am being notified of merge conflict because of: adding 4 new lines, commenting out 2 logging messages!
Maybe the reason is to be on top on developers list with the most commits to get raises (just like the nonsense competition on contribution graph on GitHub), but I am getting distracted now very often with these nonsense pushes to master.
How can I approach this issue as the least experienced person here?
professionalism communication colleagues
New contributor
Given that I am the least experienced in this place I thought in the beginning it's normal what a coworker is doing, committing and pushing nonsense changes directly to master including broken parts. I used to do the same in very extreme situations when fixing something broken or under time constraints (small sync to showcase), this doesn't seem to be the case.
For example today I am being notified of merge conflict because of: adding 4 new lines, commenting out 2 logging messages!
Maybe the reason is to be on top on developers list with the most commits to get raises (just like the nonsense competition on contribution graph on GitHub), but I am getting distracted now very often with these nonsense pushes to master.
How can I approach this issue as the least experienced person here?
professionalism communication colleagues
professionalism communication colleagues
New contributor
New contributor
New contributor
asked 10 mins ago
josi513josi513
12
12
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
josi513 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f133072%2fhow-to-deal-with-coworker-committing-and-pushing-nonsense-changes-directly-to-ma%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
josi513 is a new contributor. Be nice, and check out our Code of Conduct.
josi513 is a new contributor. Be nice, and check out our Code of Conduct.
josi513 is a new contributor. Be nice, and check out our Code of Conduct.
josi513 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f133072%2fhow-to-deal-with-coworker-committing-and-pushing-nonsense-changes-directly-to-ma%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown