Skip to content

v1.0
Compare
Choose a tag to compare
@misiektoja misiektoja released this 11 May 15:36
· 56 commits to main since this release
v1.0
15b2ba6

Initial github_monitor v1.0 release. Features:

  • Real-time monitoring of Github users activities & profile changes:
    • new events like new pushes, PRs, issues, forks, releases etc.
    • added/removed public repositories
    • added/removed starred repositories
    • added/removed followings and followers
    • changed user name, email, location, company, bio, blog URL
    • detection of account changes
  • Email notifications for different events (new events, changed followings, followers, repos, user name, email, location, company, bio, blog URL, errors)
  • Saving all user activities with timestamps to the CSV file
  • Clickable Github URLs printed in the console & included in email notifications (repos, PRs, commits, issues, releases etc.)
  • Possibility to control the running copy of the script via signals

RELEASE NOTES:

Features and Improvements:

  • NEW: Possibility to define GITHUB_TOKEN via command line argument (-t / --github_token)"
  • NEW: Possibility to limit the type of events to monitor via EVENTS_TO_MONITOR variable (if you use 'ALL' then all events are monitored)
  • NEW: Showing the latest event for the user after the tool is started
  • NEW: Added support for detecting changes in user's blog URL
  • NEW: Added support for detecting account changes
  • IMPROVE: Email sending function send_email() has been rewritten to detect invalid SMTP settings
  • IMPROVE: Strings have been converted to f-strings for better code visibility
  • IMPROVE: Info about CSV file name in the start screen
  • IMPROVE: In case of getting an exception in main loop we will send the error email notification only once (until the issue is resolved)

Bug fixes:

  • BUGFIX: Fixed the crash of the tool if the user have not generated any events yet (for example new accounts)
  • BUGFIX: Fixed the issue of duplicated events showing up as it turned out event IDs are not always returned as increasing sequentially (we assumed earlier that new event ID value is always greater than the old one)
Assets 3
Loading