My senior is lying about fixing bugs in my code to the big boss. I can’t prove it because I don’t have access to the live site files. I don’t have the rapport with the higher ups yet, what do I do?

Cut his brake lines, blackmail him, plant illicit materials on his computer and leak it to the authorities, steal his credentials and delete the site in production with tons of fingerprints.

Or find a job that uses git so there's evidence of your work that everyone had a copy of.

Shit in his coffee as soon as you guys work in the same office again

@SortOfTested I have evidence that there was no commit. I can’t prove that it wasn’t edited directly on live though

@JakobMenski
I mean, if your employer allows that, you should be looking for a move post covid.

I just had a coworker basically do the same thing.

"@Root tried making a data fix task but it left 619 records unchanged. I merged it in my task instead and it fixed all of the records. It's faster now too. and I really like how I have it organized; look!"

But she is the only person that ever ran it against real (staging?) data, since I dont have permissions yet. So she could very easily be lying. She's an unflinching braggart so I totally wouldn't put it past her.

Especially since my data fix was literally:
1) find all records where record.authorization == nil
2) if the record.x == y, set authorization to A
3) else:
3a) if record.z is in [array] set authorization to A
3b) else set authorization to B

No paths led to nil.
So 619 records left untouched? Not possible.

She also bragged that her task was faster by half ... despite it doing double the work (two data fixes) and wasn't optimized well. She's such a lying sack of crap.

@SortOfTested is it an idea to set up an local gif repo so there still is proof when it comes down to a big show down?

@Nightstrider
Git is a dvcs. Everyone has a copy of the repo.

@SortOfTested yeah but is seems op isn't under any source control

@Nightstrider I’m using git, I know there were no changes because I pulled the repo and low and behold, ‘everything is up to date’. What I can’t prove is that it wasn’t edited directly

@JakobMenski Update production. Or check after the next release: no changes, no "fixes." Your señior is lying.

Devs shouldn't be making changes in prod, and all code should be getting built, tested and deployed via a single point. That means if the application can only be changed via source control, the commit history should contain record of who completed the bug fixes.

Sounds like a garbage company anyways tbh, I agree with looking for something else post-covid.