Closed AniVerma17 closed 5 years ago
@Sc0rpi0n101 @AniVerma17 This is weird. Animesh, I think you have pulled from the wrong point of the master branch or something. Because now you have commits of @Sc0rpi0n101 which will mess up the entire master. Please rebase and fix it up.
Important points:
- Force pushing only when needed, if you are fixing up your own commits.
- You probably have pulled from an earlier part of the branch without pulling new changes first,
- Also, please try and make a new branch for development.
My bad. This happened due to an unnoticed error while syncing the fork. Has been fixed now, check.
@AniVerma17 Let me know if this post is ready to go, we can have it up this weekend.
Will finish it with meetup pics today.
Thanks, much appreciated
On Fri, Jun 14, 2019 at 12:04 PM Animesh Verma notifications@github.com wrote:
@AniVerma17 https://github.com/AniVerma17 Let me know if this post is ready to go, we can have it up this weekend.
Will finish it with meetup pics today.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/asetalias/blog/pull/45?email_source=notifications&email_token=AFN63HVRZPAN4BJ44A7NL33P2M3XPA5CNFSM4HPVEDE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXV3PJY#issuecomment-501987239, or mute the thread https://github.com/notifications/unsubscribe-auth/AFN63HRIMIEKYSCAMPDEAYLP2M3XPANCNFSM4HPVEDEQ .
Blog is completed and ready to go live. @vipulgupta2048 check.
@AniVerma17 I am not sure, this is because you are force pushing your old commits onto a new one or something else. But I am still not seeing my review about tags being implemented. Please don't force push, as we merge every PR through squash and merge.
Well I had to force push because I was squashing new commits on already pushed ones myself, because I didn't know you're merging PRs that way. Anyway, here is the final push for tags fix. And about that review, I guess you're not seeing it because I resolved it. Force push has nothing to do with that, so relax.
@vipulgupta2048 status check on this plz.
So sorry, forgot to approve this. After a short internal discussion and a lot of Hugo problems we have decided to shift to WordPress.org
Now, I know this is hugely inconvenient as well as frustrating both for the writers as well as developers working on the project. But, I think in the long run WordPress will be way more sustainable and managable.
Still merging, this, but when the time comes I would ask you for a bit of reformatting. Thanks for your contribution
Yeah, I know all the fuss Hugo caused in here, and it totally justifies this decision. And IMO shifting to WordPress would actually reduce the inconvenience, with all those GUI tools and plugins.
Resolves #14 This blog describes my experience with ALiAS during my college time. Feel free to drop suggestions.