A Place Undiscovered

I yearn for a place undiscovered,
With no one around to talk.
It will just be me unfettered;
I’ll breathe, yawp and walk.

I’ll crinkle the crisp, clean air
And chase after dragonflies;
I’ll wander here and there,
Watching suns set and rise.

I’ll sing in merry solitude,
And dance with unbound joy;
For I’ll have nothing to brood
Over, worry about or cry.⁠⁠⁠⁠

~ Pradeep CE 🙂


The Edge of Dusk

I am at the edge of Dusk,
With darkness spreading
Its inescapable blanket
Across the crimson sky.

I chaperone the dark Night,
As it creeps in from shadows
Of things inanimate,
Dimming my golden shine.

I sense the growing Evil
Diffusing like poisonous air;
Invisible, but omnipresent,
Clawing it’s way into hearts.

I stand witness in silence,
Frozen and handicapped;
Aware, but unable;
I know not what to do.

I can only kneel in prayer,
Begging for strength,
And hoping for faith
To get me through!

~ Pradeep CE.

Manually trigger Travis CI builds on Pull Requests

This tutorial deals with pull requests on Github which have Travis CI integration.

The day before this was written, Travis CI experienced some issues as a result of which some builds didn’t complete. I had a pull-request open at the time, and the build for it was stuck at “waiting for build status”.

Usually, at that point you would perform a manual build. But if you don’t have access to the repository or the Travis instance, here’s how you can trigger a manual build.

    1. Open a terminal, go to your project directory and checkout the branch from which you created the pull request.
      $ git checkout <some-cool-new-feature-branch>
    2. Amend the last commit with:
      $ git commit --amend

      When git opens your commit message, save and quit.

    3. Force-push to your feature branch.
      $ git push -f <your-fork> <some-cool-new-feature-branch>
    4. Voila! You should see a new build has been triggered.

This works because when you amend your last commit, the commit-hash changes, which leads your CI to see it as a fresh commit for which it hasn’t run the build yet. Since commit-hashes take into account the timestamp of the commit, you will always get a different hash when you perfom a git commit --amend.

A word of caution, though. This rewrites your git history, so you have to be careful when you are doing this. Ideally, don’t do this on branches that others depend on / are based off of.

Originally seen on this comment.

Where is Poetry Born?

Long ago,
And lost to thought,
Wondered did I
Where poetry was born.

The evening breeze,
The monsoon rain,
And lofty mountains
I searched in vain.

In mighty seas,
And hidden caves
I searched again,
But in vain.

In mother’s love,
A lover’s eyes,
In nature’s lap,
In sacrifice,

The cradle of poetry
I hoped to find.
But alas,
’twas in vain.

I sat me down,
The temple of poetry
Never to be found.

Then I realized
I’d always known
The voice of poetry
As my own.

So I closed my eyes,
And looked within.
The home of poetry
I was finally in!

~ Pradeep CE 🙂

The beautiful cover picture on this post is by TrufleTinker. Please drop in a word of appreciation if you liked the doodle!


As the day draws
To a close,
And night shrouds
Me in silence,

As stars peek out
From the sky,
And darkness sings
A sweet lullaby,

I think of you,
O sweet girl!
And a pain unbearable,
Claws my heart!

A silent scream,
I let slip
Into the deaf,
Starry night.

I cry, I bleed.
I hurt, but I know
That Death
Is the only relief.

~ Pradeep CE.