Current Version - 0.3 (see change logs)
Just Jobs Bot is a telegram bot which gathers detail of job opening from employer and post on the Just Jobs Channel.
To use the bot you simply have to send below mentioned commands as text message.
/start - initial command to begin talking to the bot
/help - to get help, report bug and contribute
/submit - to submit job opening in your company
The sole purpose of this bot is to get following details from the employer about the job opening.
- Company Name - This is the full name of the company
- Job Designation - Position for which this job opening is all about
- Job Description - Little detail about the job which can be also a link to document
- Joining Date - Date from when the employee's term starts
- Last Date to Apply - Date upto which a person can apply for this job
- Salary Offered - Expected salary, can also be a range.
- Contact Person - Person whom one should contact if interested
- Email Id - Email of the contact person
- Phone No - Phone number of the contact person
You need Python 3 and PIP installed for this to work
- Fork the repo to your profile
git clone link-to-repo.git
- Clone your copy of this repo to your local machinecd Just-Jobs-Bot
- Move to the repo folder- Install
pipenv
by runningpip install pipenv
- Initialize the Python 3 environment by running
pipenv --three
pipenv install -r requirements.txt
- install dependencies- Create a new bot using Botfather
- Replace
Telegram-Bot-Token
with the token you get from Botfather inconfig.txt
file - Create a channel and make it public to get the username e.g. @mychannel
- We need unique ID of this channel, to get that first add your bot as administrator to the channel you just created
- Run
pipenv run python getid.py
and sendtest
to the channel - The channel ID will be printed onto the terminal
- Replace this unique ID with
Channel-Id
inconfig.txt
file - Now run
pipenv run python justjobs.py
- You can now use commands mentioned above in
How To Use
section
- Create an issue in case you find one with the bot. Please mention how you got to that issue in brief.
- Fork this repo and create a feature/bug branch and make your changes to that.
- Create PR from feature/bug branch to master of this repo.